Mail authentication, DNS delegation and propagation, certificates, blocklists, routing and reverse DNS. Every check explains what it found, why it matters and how to fix it.
One box. A domain gets the full report, an address or a prefix gets the registry and routing record, an AS number gets what that network announces, and a URL gets the speed test.
Every tool explains what it found, why it matters and what to do about it.
Check an SPF record, count its DNS lookups the way a receiver does, and find the mechanism that pushes it over the limit.
DKIMLook up a DKIM public key, read its real size out of the record, and tell a revoked key apart from a broken one.
DMARCRead a DMARC record, and understand alignment, which is what most authentication problems actually turn out to be.
MXSee where a domain's mail is actually delivered, and whether every host in the list resolves.
RBLCheck a sending IP against the blocklists receivers actually consult.
STSCheck whether senders can be forced to use TLS when delivering to your domain, or can be silently downgraded.
RPTCheck whether you would ever hear about a failed TLS delivery to your own mail servers.
BIMICheck a BIMI record, and whether the domain is in a state where it can actually work.
Send a real message and see the DKIM, SPF and DMARC result for it, not for what your records claim.
Check a site's certificate: expiry, whether it covers the name, and whether the chain is complete.
DNSEvery record a domain publishes, read into named columns, and answered from Dhaka and Miami so you can see a name that means two different things.
NSWhat the parent says, what your nameservers say, and whether they agree.
PROPAsk eighteen independent resolvers what they are holding, compare it against your own nameservers, and see how long the stale caches have left.
SPEEDMeasure a site from Dhaka or Miami, or all three at once: where the first byte goes, what the page weighs, and whether caching and compression are actually on.
PTRCheck an IP address has a reverse name, and that the name resolves back to it.
Open a site on its new server before DNS moves, without editing hosts files.
See who registered a domain, when it expires, where its DNS points, and whether it could be moved.
IPWhose address this is: the network it belongs to, the operator announcing it, where it is registered, and who to write to about it.
ASNWhat a network announces, who carries it, and who buys transit from it.
Queries resolve through our own recursive resolver, in our data centre in Dhaka. It resolves from the root rather than reading a shared cache, which is why a result can honestly say where it was resolved from, and why there is no rate limit for ordinary use. Public resolvers sit behind it and answer only when ours cannot.
Yes. Every tool on this site, and the full report, run without an account and without payment. Paid plans exist for continuous monitoring, which is a different thing: watching a domain over time and telling you when something changes.
No. A report link is permanent. Paste it into a ticket and it will still resolve in a year, showing what was true when the check ran.
No. Reports are not listed, indexed or shared. Anyone with the link can read it, so treat the link as you would the result itself.
Bangla is being added to the explanations and fixes, not only the interface labels. A record that is wrong should be explained in the language of whoever has to fix it.