DNS/IP Lookup

DNS/IP Lookup - Check IP Address and DNS Records Online

DNS is the addressing layer that turns hostnames you can remember (wikipedia.org) into the numeric IP addresses that routers actually understand (208.80.154.224, 2620:0:861:ed1a::1). Every web request, email send, API call, and SSH connection starts with one or more DNS lookups, and when those lookups misbehave nothing else works. This tool combines three diagnostic operations developers and sysadmins reach for constantly. (1) Public IP detection — figures out the egress address your network presents to the world, useful when configuring firewall allow-lists or debugging VPNs. (2) IP geolocation — looks up the rough city/country, ISP, organization, ASN (Autonomous System Number), and timezone of any IPv4 or IPv6 address via public APIs like ipapi.co; useful for traffic-pattern analysis and abuse triage. (3) DNS record resolution — queries the global DNS over HTTPS (via dns.google or Cloudflare's 1.1.1.1) for A (IPv4), AAAA (IPv6), MX (mail), TXT (SPF/DKIM/site-verification), NS (delegation), and CNAME (alias) records for any domain. Useful for verifying that DNS changes have propagated, debugging email-deliverability issues (SPF/DKIM/DMARC), confirming your sites are running on the IPs you think they are, and exploring how big public services like Google or Cloudflare structure their DNS.

What is DNS/IP Lookup?

DNS/IP Lookup is a tool that retrieves information about IP addresses and domain names. It provides:

- IP geolocation (country, city, coordinates)
- ISP and organization information
- Hostname and reverse DNS
- DNS records (A, AAAA, MX, TXT, etc.)
- ASN (Autonomous System Number)
- Timezone and postal code

This information is useful for network troubleshooting, security analysis, and understanding internet infrastructure.

How do I use this tool?

Using the DNS/IP Lookup tool:

1. Choose lookup type:
- My IP Address: See your public IP
- IP Lookup: Get information about an IP address
- DNS Lookup: Check DNS records for a domain

2. For IP Lookup:
- Enter an IP address (e.g., 8.8.8.8)
- Click 'Lookup'
- View geolocation, ISP, and other details

3. For DNS Lookup:
- Enter a domain name (e.g., google.com)
- Click 'Lookup'
- View DNS records (A, MX, TXT, etc.)

The tool uses multiple free public APIs to ensure accurate results.

What information can I get from IP Lookup?

IP Lookup provides comprehensive information:

Location Data:
- Country, region, and city
- Latitude and longitude coordinates
- Timezone
- Postal code

Network Information:
- ISP (Internet Service Provider)
- Organization name
- ASN (Autonomous System Number)
- Hostname (reverse DNS)

This data comes from public databases and WHOIS information. Note that IP geolocation is approximate and may not pinpoint exact physical locations.

What are DNS records?

DNS (Domain Name System) records map domain names to IP addresses and other information:

Common record types:
- A Record: Maps domain to IPv4 address
- AAAA Record: Maps domain to IPv6 address
- MX Record: Mail server for the domain
- CNAME Record: Canonical name (alias)
- TXT Record: Text information (SPF, DKIM, etc.)
- NS Record: Name servers for the domain
- SOA Record: Start of authority (master server + serial)
- CAA Record: Which CAs may issue TLS certificates

DNS records are essential for websites, email, and internet services to function properly.

Why might my IP location be wrong?

IP geolocation is not always precise:

Reasons for inaccuracy:
- IP databases may be outdated
- ISPs may assign IPs regionally
- VPN or proxy changes apparent location
- Mobile networks route through different regions
- Corporate networks use centralized IPs

IP geolocation typically provides:
- Accurate country (95%+)
- Accurate region/state (80%+)
- Approximate city (60%+)
- Very approximate coordinates

For precise location, GPS is needed. IP lookup is best for regional identification, not exact addresses.

Why does the same domain resolve to different IPs from different locations?

Because the operator wants it that way. Modern large sites use GeoDNS (geographic DNS) to return different A/AAAA records depending on which DNS resolver asked: a request from Tokyo gets the Tokyo edge IP, a request from Frankfurt gets the Frankfurt edge IP, all under the same hostname. This is how Cloudflare, AWS CloudFront, Fastly, and Google Cloud route users to the geographically nearest server for low latency. It's also how Round-Robin DNS spreads load across multiple equivalent backends (your resolver receives a different order of IPs each query). Add to this CDN smart routing, Anycast addressing (where one IP literally answers from many physical locations), and split-horizon DNS (different answers for internal vs external networks), and the answer 'this domain's IP is X' becomes 'X for me, right now, from this resolver'. This tool shows you what YOUR current resolver returns; for global reach, try dnschecker.org which polls multiple regions in parallel.

What's the difference between an A record, AAAA record, and CNAME?

Each maps a hostname to a different kind of value. An A record points to an IPv4 address (4 bytes, e.g. 93.184.216.34) — the original DNS record type from 1987 and still the most-used. AAAA ('quad-A') points to an IPv6 address (16 bytes, e.g. 2606:2800:220:1:248:1893:25c8:1946) — needed because IPv4 ran out of public addresses in 2011 and modern hosts increasingly need both. CNAME ('canonical name') points to ANOTHER hostname instead of an IP — useful for aliases like 'www.example.com CNAME example.com', so changing the underlying A record once updates both. The CNAME tradeoff: it costs an extra DNS lookup (resolver fetches the CNAME, then the A/AAAA of the target), and DNS rules forbid using a CNAME on a domain's apex (you cannot have 'example.com CNAME other.com', only 'subdomain.example.com CNAME other.com') — though some providers like Cloudflare offer 'CNAME flattening' as a workaround.

How do I debug SPF, DKIM, and DMARC, and verify a CAA record before issuing a TLS certificate?

These are the two most common professional reasons to run a DNS lookup. Email authentication lives in TXT records: SPF is a single TXT on the root domain starting with 'v=spf1 ...' that lists which servers may send mail for you (look for the closing '-all' for a hard fail or '~all' for soft fail); DKIM is a TXT at '<selector>._domainkey.yourdomain.com' holding the public key (you must know the selector — e.g. 'google._domainkey' for Google Workspace — because DNS cannot enumerate it); DMARC is a TXT at '_dmarc.yourdomain.com' starting 'v=DMARC1; p=...' where p=reject/quarantine/none sets the policy. Run a DNS lookup on the domain and read the TXT block to confirm all three line up. For certificate issuance, query the CAA record: a CA (Let's Encrypt, DigiCert, etc.) is required by the CA/Browser Forum baseline to check CAA before signing, and will refuse if a CAA exists that does not list its 'issue' identifier. So before you order a cert, confirm your CAA either is absent (any CA may issue) or includes the CA you're using — this tool now resolves CAA directly.

What is reverse DNS (PTR) and why does it matter for mail-server deliverability?

Forward DNS maps a name to an IP (A/AAAA); reverse DNS (a PTR record) maps an IP back to a name, stored under the special in-addr.arpa (IPv4) or ip6.arpa (IPv6) zone. For a mail server it is close to mandatory: most large receivers (Gmail, Outlook, Yahoo) reject or heavily penalize mail from an IP with no PTR, or with a generic ISP-assigned PTR like '203-0-113-5.dynamic.example-isp.net'. Best practice is Full-Circle / FCrDNS: the IP's PTR resolves to a hostname, and that hostname's A/AAAA resolves back to the same IP, and that hostname matches your SMTP HELO/EHLO banner. Unlike forward records you control via your DNS host, PTR is set by whoever owns the IP block (your hosting provider or ISP), so you usually request it from them. This tool auto-runs a PTR lookup whenever you query an IP, so you can confirm an IP's reverse DNS in one step instead of reaching for dig -x.

What is DNS over HTTPS (DoH), and why does TTL matter for propagation?

Traditional DNS sends queries as plaintext over UDP (or TCP) port 53, which any network hop can read or tamper with. DNS over HTTPS (DoH) wraps the same query inside an ordinary HTTPS request to a resolver like Cloudflare's 1.1.1.1 (cloudflare-dns.com) or Google's 8.8.8.8 (dns.google), so it is encrypted and indistinguishable from normal web traffic — which is exactly what this tool uses, meaning every lookup runs straight from your browser with no server in the middle. TTL (Time To Live) is the number of seconds a resolver is allowed to cache a record before re-asking the authoritative server. It governs propagation: if your A record has a TTL of 3600, resolvers worldwide may keep serving the old value for up to an hour after you change it. Pros lower the TTL (e.g. to 300s) a day before a planned migration so the cutover is fast, then raise it again afterward to reduce query load. The SOA record's 'minimum' field also sets how long negative (NXDOMAIN) answers are cached.

Is my data safe?

Privacy and security:

- IP lookups query public databases
- Your searches are not logged by us
- Requests go directly from your browser to public APIs
- No personal data is stored
- IP addresses are public information

Note: When you perform a lookup, the target API providers may log the request. We use reputable free HTTPS services like ipapi.co and Cloudflare/Google DNS over HTTPS.

Your IP address is already visible to every website you visit - this tool just helps you understand what information is publicly available.

Key Features

• Get your public IP address instantly
• IP geolocation lookup (country, city, coordinates)
• ISP and organization information
• Automatic reverse DNS (PTR) lookup for any IP
• ASN (Autonomous System Number)
• Timezone and postal code
• DNS records lookup (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA)
• SOA + CAA records for zone and certificate-issuance checks
• Support both IPv4 and IPv6 (including compressed addresses)
• Multiple data sources for accuracy
• Copy results to clipboard
• Dark mode support
• Free - no API key required
• No registration needed
• Mobile-friendly responsive design