Guides
Written for whoever ends up responsible, which is usually not the person who set any of it up. Nothing gated, no account needed.
Long reads
Every failure here traces back to a process that depended on a person who left.
Read moreSilent failures cost more than loud ones, and the difference is not severity.
Read moreTwo products that look the same and answer completely different questions.
Read moreEvery business runs on something set up by someone who has left.
Read moreRenewal notices go to inboxes nobody reads and cards expire silently.
Read moreThe only outage that produces no error message on your side.
Read moreA subdomain pointing at a cancelled service can be claimed by someone else.
Read moreEvery question in a handover is historical, and history is what nobody keeps.
Read moreWhat happens between expiry and release, and where the cost curve turns.
Read moreIt arrives reliably. The problem is where it goes.
Read moreIncluding ours. The limitation is structural.
Read moreAutomation removed most failures and made the rest harder to see.
Read moreNearly every established domain has one, and nobody employed put it there.
Read moreThe questions are repetitive, and most are about duration rather than state.
Read moreFind out what you have taken on before promising anything.
Read moreIt says one day because it started today.
Read moreQuick answers
Short pages for the things people actually search. Each one links up to the full guide.
Yes, once released. Before that there is a recovery window.
Read moreTransfer lock is on, which is what you want.
Read moreUsually authentication rather than content.
Read moreUsually minutes. The 24 to 48 hours figure is mostly obsolete.
Read moreA record pointing at a service you no longer use.
Read moreThe registrar is public. The contact details usually are not.
Read moreIf your domain sends email, yes. It is also increasingly not optional.
Read moreBecause it is public and robots.txt does not restrict access.
Read moreMore often than you will, which is why it is worth automating.
Read moreDepends whether it renews automatically. If so, the expiry is a symptom.
Read moreIt lists which authorities may issue certificates for you.
Read moreThree things, often at three companies, and the confusion costs hours.
Read moreFix guides
Instructions for everything a check can find, written for someone who does not know the terminology.
Renew it, then fix the three things that caused the notice to be missed.
Read moreUsually a renewal job that stopped running somewhere nobody looks.
Read morePublishing DMARC in the order that does not block your own invoices.
Read moreThe silent failure inside a record that looks perfectly correct.
Read moreConfirming it and removing it at any DNS provider.
Read moreWorking out what is exposed and restricting it properly.
Read moreThe short version
A lapsed domain, an expired certificate, broken mail authentication and a record pointing at a dead service are different problems with different fixes. What they share is that none of them produce a warning inside your business.
Nothing crashes. No dashboard turns red. There is no error in a log you were going to read. The first signal is almost always external, and by then it has been happening for a while.
Check yours
A free check answers it in about ten seconds.