Esta página ainda não está traduzida — é apresentada em inglês.
Registration expiry date, days remaining, registrar and DNS resolution for any public domain — no account, and nothing you type here is stored.
It looks up the registration behind the domain you name and reports two things that fail independently of each other:
We look up the registrable domain, not the hostname you typed. Registration
is a property of example.co.uk, not of www.blog.example.co.uk — so if the
two differ, the tool shows you which one it actually queried rather than
quietly answering a different question.
It is the same domain check our paid monitoring runs on a schedule, exposed without an account. It runs from France, one request at a time, and stores nothing: no history, no logs of what you looked up, no results kept after the response is sent.
An expired certificate breaks the padlock. An expired domain breaks the name itself — and with it your website, your API, every email address at that domain, and every SSO callback and webhook anyone has configured against it. There is no "proceed anyway" for a name that no longer resolves.
It is also the failure with the longest recovery time. A certificate can be reissued in minutes. A lapsed domain goes through a redemption period with a restoration fee, and in the worst case is picked up by someone else while you are still finding out which former colleague's inbox the renewal notices were going to.
That last part is the actual cause almost every time. Domains are bought once, renewed silently by a card that eventually expires, and the warning emails go to whoever registered it — often years ago, often someone who has left. The registration outlives the person watching it.
From RDAP, the registries' structured replacement for WHOIS. We ask the registry responsible for that top-level domain and read the expiration event out of its answer.
Two honest caveats, because a monitoring tool that hides them is worse than useless:
.de, .ch, .it, .es,
.pt and .jp run no public RDAP service, so there is no registry server to
ask and no expiry date to read — permanently, not just today. The tool says
exactly that, rather than pretending the lookup merely glitched. .nl is the
other shape of silence: SIDN does answer, and returns a registration with no
expiration event in it. Both are reported as what they are, and neither
produces a reassuring green number we made up.DNS resolution is checked separately and always, so you get an answer about the domain even when the registry declines to give one.
Yes, and no. There is no signup, no email box and no trial. The endpoint is rate-limited per IP so that it stays available — and so we stay within what the registries allow us to ask them.
No. The lookup is stateless: your request produces one DNS resolution, one RDAP query and one JSON response, and nothing about it is written down. There is no history for you to browse and none for anyone to ask us for.
Because expiry belongs to the registration. www.blog.example.co.uk is not
registered — example.co.uk is. The tool reduces what you typed to the
registrable domain using the public suffix list and shows you both, so the
answer is never about a name you did not ask about.
There are three different answers, and the tool tells you which one you got.
If it says the top-level domain publishes no expiry data, there is no
registry server to ask: .de, .ch, .it, .es, .pt and .jp all work
this way. That is permanent, your domain is not in trouble, and your registrar
can still tell you the date.
If it says the registry answered but publishes no expiry date, we did reach
it and it simply reports registrations without an expiration event — .nl is
one such registry.
If it says we could not read the registry's answer, the lookup itself failed: a rate limit, or an unreachable registry server. This is the only one of the three where trying again shortly is worth doing, which is why it is the only one that says so.
We never report a failure as a fact about your registry, because only the first
two are facts about your domain. (.fr publishes expiry dates perfectly well,
so a French domain showing none is one of the latter two cases, never the
first.)
No. Enter a public domain name. Registrations exist for names, not addresses, and a name pointing at private address space is refused before anything is dialled — this runs from our infrastructure, not from yours.
It means the registration was valid at the moment you asked. Domains lapse on a date you will not be thinking about, which is precisely why checking by hand is not a control. A note in a calendar is not a check either — it fires whether or not the renewal actually went through.
This page tells you the state of one domain at one moment. It cannot tell you about the card that expires next March, the registrar account nobody can log into, or the renewal notice arriving at an address that bounces.
Automated domain monitoring watches the same registration on a schedule and warns you at 30, 14, 7 and 1 days before expiry — four chances to notice, the first while it is still a calendar entry rather than an incident. It watches DNS resolution continuously alongside it, and the TLS certificate sitting on top, because those three fail in different ways and on different days.
Failures are confirmed from a second independent EU probe region before anyone is paged, so a resolver hiccup in one region stays a resolver hiccup. Everything runs on Scaleway with data in France, and there is a DPA available before you ask.
The free plan covers 5 checks and does not expire.