Practical example
During a mail setup, check MX plus SPF, DKIM, and DMARC TXT records; a correct website A record says nothing about mail delivery.
Inspect DNS records and IP details, including A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, PTR, reverse DNS, and basic geo/ISP info.
Enter a domain name or an IP address to inspect DNS records, reverse DNS, and IP details.
Use these records to verify website hosting, email routing, domain ownership, certificate authorization, and reverse DNS configuration.
Maps a domain to one or more IPv4 addresses used by web servers, APIs, and other services.
Maps a domain to IPv6 addresses for networks and clients that support IPv6.
Points one hostname to another hostname, often used for CDN, SaaS, and subdomain configuration.
Defines which mail servers receive email for the domain and their priority order.
Shows the authoritative DNS servers responsible for the domain zone.
Stores SPF, DKIM, DMARC, site verification, and other domain metadata.
Contains the primary nameserver, administrator contact, serial, and timing values for the zone.
Controls which certificate authorities are allowed to issue SSL/TLS certificates for the domain.
Maps an IP address back to a hostname, useful for mail servers, logs, and network diagnostics.
Verify that A, AAAA, CNAME, and NS records point to the expected hosting provider or CDN.
Inspect MX and TXT records to confirm mail routing, SPF, DKIM, DMARC, and domain verification.
Compare DNS records after changing nameservers, moving hosting, or switching CDN providers.
Use reverse DNS and IP details to identify the hostname, provider, location, and network owner.
A DNS lookup tool lets you inspect domain records such as A, AAAA, CNAME, MX, NS, and TXT.
An IP/domain info tool helps identify reverse DNS, geolocation basics, timezone, ISP, and other useful diagnostics for infrastructure and networking work.
After checking DNS records, inspect WHOIS ownership, SSL certificates, redirects, and HTTP headers to understand the full domain setup.
Check registrar, dates, nameservers, statuses, and raw WHOIS data.
Check certificate validity, expiration, issuer, SANs, OCSP, and TLS details.
Trace HTTP redirects, inspect 301/302 chains, and verify final destination URLs.
Parse raw HTTP headers into JSON and readable key-value pairs.
Learn the workflow behind this tool and what to check next.
A layered domain launch check that catches DNS, certificate, routing, mail, and SEO mistakes before users find them.
A practical DNS checklist for website hosting, email records, domain verification, nameserver changes, SSL certificates, and reverse DNS.
A practical subnetting guide for reading CIDR notation, checking network ranges, planning private networks, and avoiding address conflicts.
Read DNS records together instead of treating one successful lookup as proof that the whole domain is configured correctly.
Confirm A and AAAA records point to the intended public endpoints and that old origin addresses are no longer returned.
Review MX priorities and the SPF, DKIM, and verification values published in TXT records before troubleshooting delivery.
Compare NS and SOA records with the authoritative DNS provider, especially after a registrar or nameserver migration.
Allow for TTL and resolver caching. A correct result from one resolver does not mean every user sees the new records yet.
During a mail setup, check MX plus SPF, DKIM, and DMARC TXT records; a correct website A record says nothing about mail delivery.
Different resolvers can return old and new answers during TTL expiry, and a CNAME chain may fail only at one intermediate name.
I compare authoritative answers with at least one public recursive resolver before calling a DNS migration complete.
You may also find these tools useful.