See your own current IP address instantly below — no lookup needed. Then enter multiple domains, one per line, and check their IP addresses, DNS records, or SSL certificate expiry in one pass.
This is the public IP address your browser is currently connecting from — no need to check a domain to see it, and no code to write.
// Results will appear here
Lookups are performed using Google's public DNS-over-HTTPS resolver, queried directly from your browser for each domain in your list. This is the same DNS system that resolves domains to IPs everywhere on the internet — the tool just gives you the raw records instead of silently using them to load a page.
Checking SSL certificate expiry requires an actual TLS handshake, which a browser can't perform against an arbitrary domain due to security restrictions. Selecting "SSL Expiry" as the record type routes the check through a small server-side helper instead, which looks up the domain's most recently issued certificate via Certificate Transparency logs (crt.sh) — no API key, and accurate for any publicly trusted certificate.
crt.sh is a free community-run service, and it's occasionally slow or briefly overloaded — you may see a timeout or a "temporarily overloaded" error even for an ordinary domain. This isn't a bug in this tool; simply retrying the lookup a moment later almost always works.
Quick summaries below; for a fuller walkthrough of what each record type actually does and the specific failures caused by picking the wrong one, see this guide to A, CNAME, and TXT records.
An A record maps a domain to an IPv4 address (like 192.0.2.1); AAAA does the same for IPv6 (like 2001:db8::1). A domain can have both, neither, or only one — if AAAA comes back empty, that domain simply isn't configured for IPv6 yet, which is still common.
MX records point to the mail servers responsible for a domain's email, each with a priority number — lower numbers are tried first. An empty MX result usually means the domain isn't set up to receive email at all, which is normal for many app or asset subdomains.
TXT records hold arbitrary text and are used for domain verification (Google Search Console, for instance), SPF/DKIM email authentication, and various ownership proofs. A domain often has several TXT records at once, each serving a different, unrelated purpose.
NS (nameserver) records list which DNS servers are authoritative for a domain — they're what your registrar points at when you change hosting or DNS providers, and they're set at the registrar level, not inside your existing DNS zone. Checking NS across a whole domain list is the fastest way to confirm a bulk migration actually finished: if a domain still shows its old provider's nameservers days after a switch, that's the domain to chase down, not the ones that already show the new provider.
The domain lookup panel tells you about a domain you type in — it never reveals your own IP. The box at the top of the page is the reverse: it shows the public IP address your own device is currently browsing from, fetched automatically the moment the page loads via a public IP-echo service (ipify), with no domain to enter and no code to write.
That specific record type may simply not exist for that domain even though the site works fine — a live website only strictly needs an A or AAAA record, not MX, TXT, or NS entries. Try switching the record type dropdown before assuming something's broken.
Yes — enter the full subdomain (like mail.example.com) exactly as you would the root domain, one per line, and it resolves independently.
DNS records are cached at multiple layers (your router, your ISP, public resolvers) for a duration set by that record's TTL. A change you make at your registrar won't be visible everywhere until every cache holding the old value expires, which is why the same lookup can return different results depending on where it's run from.
The SSL check depends on crt.sh, a free public service that isn't always perfectly reliable — it can time out or briefly return a server error even for an ordinary, unremarkable domain. This is on crt.sh's end, not a sign the domain itself has a problem. Waiting a few seconds and retrying almost always resolves it. See this post for a routine you can use to track expiry across many domains without a paid monitoring service.
There's no hard cap enforced by this tool for A/AAAA/MX/TXT/NS lookups — paste as many domains as you need, one per line. SSL Expiry checks are queued two at a time to stay polite to crt.sh's free service, so a large batch of SSL checks takes proportionally longer than the same batch of DNS record lookups.