🌐 Internet Tools
IP lookup, browser fingerprint, and network diagnostics
Your public IP address and geolocation
Open tool →What your browser reveals about you
Open tool →Look up DNS records for any domain — A, AAAA, MX, CNAME, TXT and more.
Open tool →Inspect HTTP response headers for any URL.
Open tool →Look up domain registration details — owner, registrar, expiry date.
Open tool →Check SSL/TLS certificate details for any domain.
Open tool →Lookup tools for the questions that come up when something on the network is not behaving: what does this domain actually resolve to, is that certificate about to expire, what headers is the server really sending, and what does the outside world see when I connect.
These are the few tools on the site that must talk to something else — a DNS answer cannot be computed locally. Each sends only the host name you typed, and nothing is logged against you.
Which tool do I want?
| If you… | Use |
|---|---|
| You want to know your public IP as seen from outside | What's My IP |
| A domain resolves oddly and you want the records | DNS Lookup |
| You need registration and ownership for a domain | Whois Lookup |
| You are debugging caching, redirects or CORS | HTTP Header Inspector |
| A certificate is expiring or the chain is broken | SSL Certificate Checker |
| You want to see what your browser reveals | Browser Info |
DNS propagation is really just caching
"Waiting for propagation" describes something that does not happen. DNS records are not pushed anywhere — every resolver holds its own cached copy and keeps it for as long as the record's TTL says, then asks again. The delay you experience is other people's caches expiring at their own pace.
Which gives you a lever. Lower a record's TTL to 300 seconds a day before you plan to move it, and resolvers will start discarding their copies within five minutes of the change. Make the change, confirm it, then put the TTL back up. Skip that step and a record with an 86400 TTL can serve the old address to some users for a full day.
It also explains why a lookup here can disagree with what your laptop does. This tool queries a public resolver; your machine may be answering from its own cache, your router's, or your ISP's. Different caches, different ages, different answers — all of them technically correct.