All systems operationalReal-time DNS, email and infrastructure monitoring
SupportAPIContactSign in
PLAYBOOK

Practical guides to domains that must work.

Why each part of DNS, email authentication and monitoring matters — what breaks when it is missing, and how to check yours in under a minute.

Domain health score gauge and category bars86B · Domain HealthBlacklist100Mail server70Email auth55Web & SSL100DNS92Registration100Fix the red category first — it is the one costing you deliveries today.
Monitoring8 min read

How to Read a Domain Health Report and What to Fix First

A score is only useful if it tells you what to do next. Here is exactly how the StatusDNS health score is calculated, and the order to work through the findings.

Read the guide →
MTA-STS policy enforcing TLS between mail serversSending servergmail.comYour MXmail.example.com_mta-sts TXTv=STSv1; id=20260901https://mta-sts.example.commode: enforce · mx: mail.example.comSTARTTLS · valid certificate · TLS 1.2+Downgrade attempt → refused, reported via TLS-RPT
Email deliverability11 min read

Making SMTP Encryption Something You Can Rely On

STARTTLS is optional by design, and anyone in the network path can remove the offer. MTA-STS and TLS-RPT turn "we probably used TLS" into something you can require and verify.

Read the guide →
Bulk sender requirements checklistBulk sender requirements — Gmail · Yahoo · MicrosoftSPF and DKIM on every sending domainDMARC record (p=none is enough to start)From domain aligned with SPF or DKIMValid forward and reverse DNS (PTR)TLS on every connection!One-click List-Unsubscribe (RFC 8058)!Spam rate below 0.3 % in Postmaster Tools
Email deliverability10 min read

The Bulk Sender Checklist for Gmail, Yahoo and Microsoft

Since February 2024 the large mailbox providers stopped treating authentication as optional. Here is the full checklist and what happens when you miss an item.

Read the guide →
Forward-confirmed reverse DNS loopSending IP203.0.113.25PTR record25.113.0.203.in-addr.arpaHost namemail.example.comA recordmail.example.com → 203.0.113.251. reverse2. name3. forward4. same IP ✓FCrDNSforward-confirmed reverse DNS
DNS8 min read

Why Mail Servers Judge Your IP by Its PTR Record

Reverse DNS is the one mail setting you cannot fix in your own DNS zone. Here is what receivers check, why a missing PTR costs you delivery, and how to get one.

Read the guide →
DNS record set before and after a changeYesterday 03:00 (baseline)MX 10 mail.example.comMX 20 mail2.example.comNS ns1.provider.netNS ns2.provider.netTXT v=spf1 include:_spf.google.com -allA 203.0.113.10Today 03:00 — 3 changes detected MX 10 mail.example.com- MX 20 mail2.example.com NS ns1.provider.net- NS ns2.provider.net+ NS ns1.unknown-host.ru+ TXT v=spf1 +allEvery run snapshots NS, MX, A/AAAA, SPF, DMARC and CAA and diffs them against the last run.
DNS10 min read

Who Changed That DNS Record?

Zones drift — agencies, ex-vendors, a developer "just testing". Most changes are harmless and one is a hijack. You cannot tell them apart without a baseline.

Read the guide →
Monitoring alert versus customer complaint timelineWith monitoringDNS change / listing03:00Next check03:05Alert email / Slack03:06Fixed08:30Without monitoringSame changeMonday 03:00mail bouncing · nobody knowsCustomer complainsThursdayFixedFridayThe problem is identical. What changes is who finds out first — and how long it costs you.
Monitoring9 min read

Why Checking Once Is Not the Same as Monitoring

A green check is a statement about one moment. Most domain failures happen quietly afterwards — here is how to think about detection time, and what to watch.

Read the guide →
Certificate chain: leaf, intermediate, rootLeafstatusdns.com · 90-dayexpired 3 days agoIntermediateR11 · Let’s EncryptvalidRootISRG Root X1validRenewed on the server…The certbot log says “renewed”, but the web server was never reloaded — visitors still get the old, expired leaf.A browser needs every link of the chain to be valid and served. Monitoring reads what visitors actually receive.
Security10 min read

Your Certificate Renewed. It Just Never Reached the Server.

Renewal is not deployment. The classic outage is a certificate issued perfectly on time, sitting on disk, while the running service still serves the expired one.

Read the guide →
DMARC rollout timeline from none to rejectp=noneWeek 0–4Collect reports, fix sendersReports: mostly failquarantinepct=25Small share to spamReports: improvingquarantinepct=100All failures to spamReports: ≥ 98% passp=rejectEnforcedSpoofed mail rejectedReports: stableOnly move to the next stage when aggregate reports show your legitimate senders alignedv=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc@yourdomain.com; adkim=r; aspf=r
Email deliverability11 min read

From p=none to p=reject Without Breaking Your Mail

Publishing an enforcing policy on day one is how legitimate mail disappears. Here is the staged path, plus what to do about forwarding and mailing lists.

Read the guide →
Domain expiry countdown with reminder markersRegistration expiry — countdown60 dreminder30 dreminder14 dreminder7 dreminder3 dreminder1 dreminderDay 0offlineWhen a domain lapses, website, email, DNS and every subdomain stop at once.Reminders from a registrar go to one mailbox; alerts from monitoring go to your team.Registrar lock ✓Auto-renew ✓Card on file ✓
Security9 min read

The Outage Nobody Plans For: Your Domain Expires

A lapsed domain takes down your website, your email and every login at once — and it almost always happens because of an expired card, not a decision.

Read the guide →
SPF include tree exceeding the 10 DNS lookup limitv=spf1 include:… -all0include:_spf.google.com1include:sendgrid.net2include:spf.protection…3_netblocks.google.com4_netblocks2.google.com5include:… (vendor)6spf-a.outlook.com7spf-b.outlook.com8a:mail.vendor.net9mx10include:legacy-crm.io1111 / 10 lookupsPermError → SPF fails
Email deliverability9 min read

The SPF 10-Lookup Limit and the Silent PermError

Add one more vendor to your SPF record and mail can start failing for everyone — with no bounce, no error in your sending dashboard and nothing in your logs.

Read the guide →
The blacklist cycle: compromise, listing, bounces, delistingCompromised mailboxor open relay1Spam sent fromyour IP2Spamhaus / SpamCoplist the IP3Bounces & spamfolder for all mail4Fix the cause,request delisting5Monitor so itnever repeats6The blacklistcycle
Monitoring9 min read

How Email Blacklists Work, and How to Get Off One

A blacklist listing stops your mail at the door, usually without warning. Here is how listings happen, what they cost, and how to get removed without being re-listed a week later.

Read the guide →
How a receiving mail server checks SPF, DKIM and DMARCYour mail serverSPF recordIs this IP allowed?DKIM public keyIs the signature valid?DMARC policyDo they align? What now?Receiving serverGmail, Outlook, Yahoo…InboxSpamRejectSends a messagefrom you@example.com
Email deliverability10 min read

SPF, DKIM and DMARC: How a Receiver Actually Decides

Follow one message from your server to somebody's inbox and see exactly where each protocol is consulted — and why two out of three is often the same as none.

Read the guide →

Stop reading, start checking.

Run a free Domain Health report — no account needed — or monitor your domains continuously from $89 a year.