New Domain Readiness
/readinessEnter a newly bought sending domain and get a pre-launch verdict: its age, its authentication, whether a website answers, and a warmup schedule for the first weeks.
The date is optional. It is only used when the registry won't answer a browser lookup. Read live from RDAP and public DNS; nothing is stored.
What a readiness check is
- What it is
A pre-flight check for a sending domain: how old it is, whether SPF, DKIM and DMARC are in place, and whether anything answers at its website.
- Why it matters
A new domain with no records and no history is the shape of every phishing domain. Receivers filter it fast, and reputation is slow to rebuild.
- Without it
Without it, the usual story is a burned domain in week one and a new domain in week two.
What we check
- Registration date from the registry's RDAP service, turned into an age in days
- MX, SPF, DKIM (common selectors) and DMARC, read from public DNS
- Whether
https://yourdomain/answers at all - Which tools are already visible in DNS, so you know what is set up and what is not
Common questions
How old should a domain be before I send from it?
There is no published rule. Most teams give a new domain two to four weeks, with mailboxes exchanging real replies in that time, before any real volume. Under two weeks, receivers see a domain with no history and nothing to trust.
Why did the age come back unknown?
Some registries do not allow browsers to read their RDAP service, and some TLDs have no RDAP service at all. Enter the registration date from your registrar's receipt and run again; it is used only for the age check.
The website check says it answered, but I set up a redirect. Does the tool see that?
No. A browser can only tell that something answered at the address; it cannot read where a cross-origin redirect went. Open the address yourself to confirm it lands on your main site.