LookMyIPLookMyIP

Methodology

How we gather, refresh, and verify the data behind every tool

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.

ToolSourceRefresh
IP Geolocation, ASN, ISPipinfo.ioOn every lookup
WHOIS / RDAPDirect RDAP queries to authoritative registries (Verisign, Afilias, ARIN, RIPE, APNIC, LACNIC, AFRINIC)On every lookup — no caching of WHOIS responses
DNS RecordsDNS-over-HTTPS to Cloudflare 1.1.1.1 with Google 8.8.8.8 as fallbackLive, respects upstream TTLs
DNS PropagationParallel DoH queries to 10+ public resolvers (Cloudflare, Google, Quad9, OpenDNS, AdGuard, NextDNS, Comodo, etc.)Live on every check
DNSSECDirect DNS queries for DS, DNSKEY, and RRSIG records, plus chain-of-trust walk from the root zoneLive on every check
Reverse DNS / PTRLive PTR query against the IP address arpa zone, plus forward A/AAAA verification (FCrDNS)Live
SSL CertificateDirect TLS handshake against the target host on port 443Live
IP ReputationAbuseIPDBLive on every lookup
IP Blacklist20+ DNS-based blocklists (Spamhaus, SORBS, Barracuda, SpamCop, etc.)Live DNS query per blocklist
MX RecordsLive DNS queryLive
SPF / DKIM / DMARCLive DNS query for TXT records at the SPF, DKIM selector, and _dmarc subdomainLive
HTTP HeadersDirect HTTP request to the target URL from our serverLive
Redirect ChainSequential HTTP requests following Location headers, capturing each 301/302/307/308 hopLive
Open Port CheckTCP connect from our infrastructure to the targetLive

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: Authoritative — reflects current DNSSEC status as published by the zone operator and the registry. Does not cache.
  • 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: Authoritative — what each DNSBL operator currently publishes.
  • MX Records: Reflects current authoritative DNS for MX records.
  • SPF / DKIM / DMARC: SPF / DMARC parsing follows RFC 7208 and RFC 7489. DKIM lookup verifies a specific selector when provided.
  • 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.