Registrar agnostic · Portfolio ops

All domain registrars, one monitoring view.

Aepto monitors domains at any registrar, including GoDaddy, Namecheap, Cloudflare, Google and Porkbun, without moving them. Add your domains and every registrar's names appear in one list.

The multi-registrar mess, mapped not migrated

Same portfolio. Different logins. One queue after you import.

  • Agencies and investors rarely keep every name at one registrar.
  • Deals land at whichever marketplace had the price.
  • Hosting moves DNS to Cloudflare while the name stays elsewhere.
  • Spreadsheets cover this until a renewal email lands in a dead inbox, or an unauthorised nameserver change goes quiet for a week.
  • Aepto works with any registrar: import the inventory, attach monitors, and work from Requires Your Attention.
Namecheap Client microsites
Cloudflare DNS + proxy
GoDaddy Legacy brand
Google Workspace bundles
Porkbun Investor picks
Route 53 AWS side projects

After import: one Attention surface

  • 01 Uptime, SSL, and PageSpeed (PageSpeed included on Free)
  • 02 DNS history plus Theft Guard baseline
  • 03 Renewals via expense tracking
  • 04 Paid webhooks when the team outgrows root email

What stays at the registrar vs what Aepto owns

What Aepto covers, and what your registrar still does.

RegistrarOwns
  • Registration and renewals
  • Locks, 2FA, WHOIS contacts
  • Auth codes and transfers

Where money and legal control still live.

AeptoSees
  • Uptime and slow response
  • SSL windows and DNS drift
  • Renewal reminders and folders

The ops layer across every registrar you already use.

Inventory that respects where names already sit

  • Folders by client, project, or registrar give you a mental model without a transfer cart.
  • Quick Add pulls public metadata so the first pass is fast: you are not retyping NS hosts by hand for fifty names.
  • When something breaks, you still fix DNS or hosting at the right vendor.
  • Aepto tells you which name is on fire, which SSL is inside the window, and whether the Attention item is uptime, content, or drift.

Aepto does not register or renew names, and it does not replace registrar locks or 2FA. See Pricing for domain limits and paid unlocks like Content Monitoring and webhooks.

Adding domains to Aepto from any registrar

Why registrar sprawl creates false calm

Each panel looks fine. The portfolio does not.

Renewal blind spots

Auto-renew fails on one registrar while you stare at another. Central reminders beat five calendar notes.

Silent DNS moves

NS changes do not always email every stakeholder. Baseline alerts surface drift even when the registrar UI looks ordinary.

Uptime without context

A ping tool may watch the site. It rarely knows which folder, client, or renewal window that hostname belongs to.

What stays at the registrar, and what does Aepto take over?

Monitoring works wherever your names already sit. Nothing has to move.

Registrar versus Aepto responsibilities
TaskRegistrarAepto
Renew and payYesReminders and cost tracking
Transfer lock and 2FAYesAlerts if registrar or nameservers drift
Edit DNS recordsYes, or your DNS hostChange history and emails
Every domain in one listNoYes
Uptime, SSL and content checksNoYes
Move names between registrarsYesNot needed for monitoring

What habits keep a multi-registrar portfolio under control?

Import is the start. Owning the queue is the habit.

  • One named owner reviews Requires Your Attention every day.
  • Transfers are planned projects with locks, 2FA and a set window.
  • Folders separate production names from experiments.
  • A monthly renewal review, even when auto-renew is on.
  • Theft Guard on every production name.
  • Costs reviewed next to the inventory, not across invoices.

What is the same at every registrar?

For generic TLDs, ICANN policy sets the common ground.

clientTransferProhibited

is the status code behind the usual "registrar lock". It blocks transfers, not DNS edits

Source: ICANN

~30 and ~7 days

before expiry: when registrars must send renewal reminders for generic TLDs, to the registrant email on file

Source: ICANN ERRP

60 days

transfer lock that follows a change of registrant, unless you opt out

Source: ICANN Transfer Policy

Common questions

Do I have to transfer domains to Aepto?

No. Domains stay at your registrars. Aepto is the operations layer: monitoring, renewals visibility, DNS baseline alerts, and the Attention queue. It is not a registrar or marketplace.

How do I add domains from different registrars?

Quick Add AI and bulk import read public WHOIS and DNS metadata so you can centralize inventory without moving names. You still renew and lock at each registrar.

Does registrar choice change monitoring quality?

Checks run against your live site and public DNS/SSL signals, independent of where the name is registered. Theft Guard learns a baseline regardless of registrar.

Can Aepto renew or lock domains for me?

No. Renewal and clientTransferProhibited locks happen at the registrar. Aepto reminds you, surfaces cost, and alerts on drift. It does not place renewals or act as a lock.

What if my team uses five registrar logins today?

Import the book once, folder by client or project, and use one Attention queue instead of hopping panels when something fails.

Do I have to move every domain to one registrar?

No. Aepto tracks domains as assets across registrars. Consolidation can be a later project; visibility should not wait on migrations.

What breaks when registrars multiply?

Different lock labels, renewal emails, and UIs, with no single weekly triage list. Inventory and Attention restore that list.

Keep your registrars. Lose the tab chaos.

Free for 3 domains. Same monitoring stack regardless of where the name is registered.

Aepto domain inventory listing many domains with registrar and renewal details