DNS lookup (DNS over HTTPS)
Query any DNS record type straight from your browser over DNS-over-HTTPS. Pick Cloudflare or Google as the resolver and see the answers with TTLs, plus a dig-style raw view. The lookup goes directly from your browser to the resolver; this site's servers never see it.
Queries go straight from your browser to the resolver over HTTPS. This site's server never sees what you look up. Pasting a full URL works too: the scheme and path are stripped automatically.
Results
DNSSEC: these answers were validated with DNSSEC by the resolver (AD flag set).
Raw view (dig style)
Want the full security posture, not just one record? Scan this domain for TLS, security headers, email posture and hosting in one free report.
What is DNS over HTTPS?
DNS over HTTPS (DoH) wraps an ordinary DNS query inside a regular HTTPS request to a public resolver, here either Cloudflare (1.1.1.1) or Google (8.8.8.8) via their JSON endpoints. Because the request leaves your browser and goes directly to the resolver, this page's server is never involved: the lookup stays between you and the resolver you picked. The tradeoff is that you are trusting that public resolver instead of the one your network assigned, and some corporate or filtered networks block public DoH endpoints outright (which is exactly when the resolver switch above earns its keep).
Do not be surprised if Cloudflare and Google return different answers for the same name. Both run anycast networks with hundreds of locations, so your query may land in different cities, and CDNs deliberately hand out addresses close to whichever resolver asked (geo-routing). Caching adds more drift: each resolver holds answers for up to the record's TTL, so one may serve a fresh record while the other still serves the previous one. Neither answer is wrong; they are two valid views of a distributed system.