Where the data comes from
Every tool on LookMyIP is backed by a clearly identified source. Where we use a third-party API, we name it. Where we query the public internet directly, we say so. Nothing is faked, simulated, or filled in from cached guesses.
| Tool | Source | Refresh |
|---|---|---|
| IP Geolocation, ASN, ISP | ipinfo.io | On every lookup |
| WHOIS / RDAP | RDAP via the rdap.org bootstrap, which redirects each query to the authoritative registry or RIR (Verisign, Identity Digital, ARIN, RIPE, APNIC, LACNIC, AFRINIC and others) | Cached for up to 1 hour per query |
| DNS Records | DNS-over-HTTPS to Cloudflare 1.1.1.1 | Live, respects upstream TTLs |
| DNS Propagation | Parallel DoH queries to 8 public resolvers (Cloudflare, Google, OpenDNS, AdGuard, NextDNS, DNS.SB, Control D, AliDNS) | Live on every check |
| DNSSEC | DS and DNSKEY queries over DNS-over-HTTPS, with validation status (the AD flag) from Cloudflare’s validating resolver | Live on every check |
| Reverse DNS / PTR | Live PTR query against the IP address arpa zone, plus forward A/AAAA verification (FCrDNS) | Live |
| SSL Certificate | Direct TLS handshake against the target host on port 443 | Live |
| IP Reputation | AbuseIPDB (abuse reports, usage type, Tor exit status) | Live on every lookup |
| IP Blacklist | 10 DNS-based blocklists (Spamhaus ZEN, Barracuda, SpamCop, UCEPROTECT L1/L2, DroneBL, Backscatterer, Mailspike, PSBL, Truncate) | Live DNS query per blocklist |
| MX Records | Live DNS query | Live |
| SPF / DKIM / DMARC | Live DNS query for TXT records at the SPF, DKIM selector, and _dmarc subdomain | Live |
| HTTP Headers | Direct HTTP request to the target URL from our server | Live |
| Redirect Chain | Sequential HTTP requests following Location headers, capturing each 301/302/307/308 hop | Live |
| Open Port Check | TCP connect from our infrastructure to the target | Live |
Accuracy claims
- IP Geolocation, ASN, ISP: Country: ~99%. City: 80–90% (within 25–50 miles). Street-level precision is not possible from IP geolocation alone — anyone claiming otherwise is wrong.
- WHOIS / RDAP: Authoritative; reflects registrar updates within minutes to hours of a change.
- DNS Records: Reflects what DoH resolvers see at query time. May lag authoritative changes by the record TTL.
- DNS Propagation: Shows resolver-by-resolver state. A resolver lagging here means its cache has not yet expired.
- DNSSEC: Reflects whether a validating resolver accepts the zone’s signatures right now. We report the resolver’s verdict rather than re-verifying each signature ourselves.
- Reverse DNS / PTR: Authoritative; reflects the current PTR record and its forward-confirmation status.
- SSL Certificate: Authoritative; reflects the cert the server is currently presenting.
- IP Reputation: Reflects AbuseIPDB community reports. Confidence score 0–100; >50% warrants investigation.
- IP Blacklist: What each DNSBL operator currently publishes. Spamhaus refuses queries from cloud resolvers, so it is usually reported as “could not check” with a link to its own lookup; lists that stop answering their test entry are removed.
- MX Records: Reflects current authoritative DNS for MX records.
- SPF / DKIM / DMARC: SPF / DMARC parsing follows RFC 7208 and RFC 7489, including the policy inherited through an SPF redirect=. DKIM needs a selector: we try common ones, or the one you enter.
- HTTP Headers: Authoritative; what the server returns to a real request.
- Redirect Chain: Reflects the current redirect chain at request time. Hop count is capped to prevent loops.
- Open Port Check: Reflects firewall + routing reachability from our network. Local firewalls between us and the host can affect results.
Editorial standards
- No undisclosed paid placements. No tool result is influenced by sponsorship, affiliate relationships, or paid inclusion. If a future feature involves any of those, we will label it inline at the point where it appears.
- Factual content is reviewed. Every blog post and knowledge base entry is reviewed against authoritative sources (RFCs, IANA / IETF documents, registry policies, and primary vendor documentation) before publication. Posts include a Last updated date.
- Corrections are visible. When we discover a factual error, we correct the post and bump the Last updated date so the change is visible in the metadata and to anyone who has linked to the page.
- No personal data is sold or shared. We do not sell, rent, or share user data with third parties for advertising. See our Privacy Policy for the full disclosure.
- No tracking-heavy ads. The site is supported by the same small team that runs our other free projects (see our other projects).
Reporting an issue
If a result looks wrong, or if a piece of content is out of date, please let us know. Including the input you used (IP, domain, URL) and what you expected vs. what you saw makes the fix faster.