Blacklist and DNSBL status
See whether the domain appears on checked DNSBLs and which A records are associated with it. A clean result is useful, but it is only a point-in-time reputation signal — it does not guarantee inbox placement.
Check a domain’s blacklist status, SPF, DKIM, and DMARC records at once
| Domain | A record | Blocklist | SPF | DKIM | DMARC |
|---|
A healthy sending domain needs more than a clean blacklist result. This checker brings together reputation signals and the DNS authentication records mailbox providers use to decide whether a message is trustworthy.
See whether the domain appears on checked DNSBLs and which A records are associated with it. A clean result is useful, but it is only a point-in-time reputation signal — it does not guarantee inbox placement.
SPF identifies the hosts and services allowed to send mail for the domain. The detailed result follows included records and DNS lookups so you can spot an invalid record or a lookup limit problem.
DKIM publishes a public key under a selector. Use auto detection to check common provider selectors, or enter the selector used by your sending service to inspect its record directly.
DMARC tells mailbox providers how to handle unauthenticated mail. A published record is the starting point; effective protection also depends on SPF or DKIM passing with domain alignment.
If a domain is listed, review recent sending activity, complaint rates, compromised forms, suspicious links, unauthorized senders, and the specific list’s removal process. Fix the root cause before requesting delisting.
An invalid SPF, DKIM, or DMARC result can reduce trust in legitimate messages and make spoofing easier. Confirm each sending platform is authorized, signs messages correctly, and remains aligned with the visible From domain.
Marketing, transactional, billing, and notification streams can use different subdomains and providers. Review each sending domain separately so a problem in one stream does not remain hidden by another.
A manual lookup helps troubleshoot a current problem. Continuous monitoring helps you catch reputation changes, unauthorized senders, and authentication regressions before they affect delivery.