Domain X-ray
One query, one report: registration, nameservers, hosting, CDN, WAF, mail, certificate, DNSSEC, and every DNS record.
About the Domain X-ray
Domain X-ray runs a full infrastructure fingerprint of a domain in a single query and consolidates the result into one report: who it is registered with and when it expires, its nameservers, the hosting and CDN in front of it, any web application firewall, the mail provider, the live TLS certificate, DNSSEC status, and every DNS record. Instead of opening ten separate tools, you get the whole picture at once.
Each section is drawn from a public source our server queries directly: registration from RDAP, records over DNS-over-HTTPS, the certificate from a live TLS handshake, and hosting, CDN, and firewall from the HTTP response. There is no paid intelligence API behind it, and the domain you enter is not stored. Hosting, CDN, and WAF detection is a best-effort fingerprint from nameservers and response headers, so treat those as strong hints rather than a guarantee.
Use it to audit a domain you are migrating, vet a third party before trusting it, or get your bearings on an unfamiliar site. For a single dimension in more depth, reach for DNS Lookup, SSL Checker, or Email Health.
Reach the developers and engineers who use these tools every day.
Frequently asked questions
How is this different from the individual DNS, SSL, and domain tools?
It runs all of them at once against the same domain and merges the output into one report, then adds hosting, CDN, WAF, and mail-provider detection on top. The single-purpose tools still exist when you want to focus on one area.
How are hosting, CDN, and WAF detected?
From signals the other lookups already return: the nameservers, the response Server header, and distinctive headers such as cf-ray or x-amz-cf-id. It is a fingerprint, not a declared fact, so a result of "not detected" only means no known signal was present.
Does the DNSSEC line fully validate the chain of trust?
No. It reports whether a DNSKEY exists at the apex and whether the resolver set the Authenticated Data bit. That is a reliable signed/unsigned signal, not a full chain validation.
Why do some sections say they could not be read?
Each source is queried independently and allowed to fail on its own. A domain with no website still returns registration and DNS; a host that blocks probes still returns its certificate. You get whatever is reachable.
Is the domain I enter stored?
No. The lookups run on our server against public sources and the result is returned to you. The domain is not logged or persisted.