Free DNS, SSL and email checking tools

Tools for checking domains, websites and mail. No registration needed, and they work for any domain.

Domain and DNS

Website and server

Email

What these tools are for

A domain that carries a website and mail is set up in several places: at the registry, on the nameservers, on the web server and at the mail provider. A mistake in any one of them usually shows up somewhere else: the site does not load, mail lands in spam, or the browser warns about the certificate.

These tools read the settings from outside, as the rest of the internet sees them, and say in plain language what is wrong and what to do about it. They are free, need no registration, and work for any domain, not only those hosted at aWh.

Every report can be saved and sent as a link, which stays available for 14 days. That helps when you ask your hosting provider or your developer for help. The DNS, SSL and mail checks also show what has changed since the domain was last checked.

Which tool for which problem?

The website does not load
Start with the reachability test: it tells a site that is down from one that only you cannot reach. If nobody can reach it, the DNS check shows whether the domain still points to the right place, and the SSL check whether the certificate has expired.Reachability and Response TimeDNS CheckSSL Check
Mail lands in spam or bounces
Receiving servers look at three records: SPF, DKIM and DMARC. Check all three, and if you run your own mail server, its reverse DNS as well.SPF CheckDKIM CheckDMARC CheckIP Address Info
The browser warns about the certificate
The SSL check shows whether the certificate has expired, is issued for a different name, or the server sends an incomplete chain.SSL Check
You are moving to a new host or new nameservers
Before and after the move, look at what the nameservers answer, and look up single records to see whether a change has reached the public resolvers. If the domain is protected by DNSSEC, check the chain first: that is where a move most often takes a domain offline.DNS CheckDNS Record LookupDNSSEC Chain
You want the site to be safer for its visitors
The security headers check grades what the site tells browsers to refuse, and says what else to set.Security Headers
You want your logo to show next to your mail
BIMI needs a strict DMARC policy, a logo in the right format and, for Gmail and Apple Mail, a certificate. The BIMI check goes through each of them.BIMI CheckDMARC Check

Frequently asked questions

Are the tools really free?

Yes. There is nothing to pay and nothing to register for. To keep the service fast for everyone, one visitor can start up to ten new checks a minute.

Can I check a domain that is not hosted at aWh?

Yes, any domain or server that can be reached from the public internet. The tools read only what is public anyway: DNS records, the certificate a server presents and the headers a website sends.

Where do the checks run from?

Mostly from Cloudflare's network. The DNS check asks the domain's authoritative nameservers directly, the record lookup shows what Cloudflare's public resolver (1.1.1.1) answers, and the SSL and security headers checks connect to the server itself. What Cloudflare's network cannot do is done from an AWS data centre in Frankfurt: DNS questions over UDP, the HTTP/3 test, reaching servers behind Cloudflare, and asking the registries' WHOIS servers. The .hu registry's WHOIS server is asked from a server in Budapest first, as it limits queries from abroad far more strictly. The DKIM check shares its search for selectors out among AWS and Google Cloud data centres and the server in Budapest. The reachability test measures from your own browser, and for comparison from AWS and Google Cloud data centres and the server in Budapest.

What do "Error" and "Warning" mean in a report?

An error is something that does not work or soon will not: a nameserver that does not answer, for example, or an expired certificate. A warning still works today but is worth fixing. "Info" is something worth knowing, with nothing to do.

I found a problem. Where do I fix it?

Every finding says what to do. Where to do it depends on the setting: DNS records with whoever runs the domain's nameservers, nameservers and DNSSEC keys at the registrar, the certificate and the headers on the web server. If the domain is hosted at aWh, our support is glad to help: save the report and send us its link.