A Record Lookup - Find IPv4 Address for Any Domain
No logs stored • Server-side processing
Find IPv4 addresses, TTL values, and verify domain-to-IP mappings for any domain. Check multiple A records for load balancing. Supports all 8 DNS record types.
Free Online A Record Checker
Enter a domain above to get started
We'll show you A, AAAA, MX, CNAME, TXT, NS, SOA, and CAA records
What is an A Record?
An A record (Address record) is the most fundamental DNS record type. It maps a domain name to an IPv4 address, telling browsers and servers where to find your website. When you type 'example.com' into your browser, a DNS A record lookup finds the IP address (like 93.184.216.34) where the site is hosted. Every website accessible via a domain name needs at least one A record.
What You'll Discover
Can Find
- IPv4 addresses (A records) for any domain
- TTL values showing how long records are cached
- Multiple A records for load-balanced domains
- DNSSEC status (signed or unsigned)
- All 8 DNS record types via tabs (AAAA, MX, CNAME, TXT, NS, SOA, CAA)
Cannot Find
- IPv6 addresses (use AAAA Record Lookup)
- Real-time DNS propagation status (use DNS Checker)
- Hosting provider details (DNS shows IPs, not provider names)
- Historical A record changes
How to Check A Records
Find IPv4 addresses for any domain in seconds
Enter the Domain
Type the domain or subdomain you want to check (e.g., google.com or www.google.com). URLs with https:// and www prefixes are automatically cleaned.
Click Lookup
We query DNS servers to retrieve all A records. Multiple A records indicate load balancing or CDN usage.
View IPv4 Addresses
See all IPv4 addresses the domain points to, with human-readable TTL values. Use the copy button to quickly copy any IP address.
Explore Other Records
Switch tabs to view AAAA (IPv6), MX (mail), CNAME (alias), TXT, NS, SOA, and CAA records—all from one lookup.
Understanding Your A Record Lookup Results
What each field in your A records reveals
IPv4 Address
The 32-bit IPv4 address where the domain is hosted. This is the actual server address browsers connect to. Displayed in dotted-decimal notation (e.g., 93.184.216.34). Click the copy button to copy any address.
93.184.216.34
TTL (Time To Live)
How long DNS resolvers cache this A record before checking for updates. We display TTL in human-readable format: '5m' = 5 minutes, '1h' = 1 hour, '24h' = 24 hours. Lower TTL means faster propagation of changes but more DNS queries.
6h (21600 seconds)
Record Count
The number of A records for the domain. Multiple A records indicate load balancing (traffic distributed across servers), redundancy (failover if one server fails), or CDN usage (different IPs based on location). DNS may return records in round-robin order.
3 A records
DNSSEC Status
Whether the domain has DNSSEC (DNS Security Extensions) enabled. DNSSEC adds cryptographic signatures to DNS records, preventing spoofing and cache poisoning attacks. Green = enabled with DNSKEY and DS records.
Enabled ✓
Response Time
Time taken to query and return all DNS records. Cached queries are faster (< 50ms) than fresh lookups (< 500ms). Slow responses may indicate DNS server issues or network latency.
156ms
Why Choose Our A Record Lookup Tool
More than just A records—complete DNS visibility
A Record Focused
Opens directly on the A records tab for instant IPv4 address visibility. No hunting through menus—get the information you need immediately.
8 DNS Record Types
A records are the default, but AAAA, MX, CNAME, TXT, NS, SOA, and CAA are available via tabs. One lookup gives you the complete DNS picture without switching tools.
Human-Readable TTL
TTL values displayed as '5m', '1h', '24h' instead of confusing seconds. Instantly understand how long records are cached without mental math.
One-Click Copy
Click any IPv4 address to copy it to your clipboard instantly. Perfect for pasting into server configurations, firewall rules, or documentation.
DNSSEC Detection
See at a glance whether the domain has DNSSEC enabled. A security indicator shows if DNS responses are cryptographically signed and validated.
Export to JSON/CSV/TXT
Download your A record lookup results in multiple formats. JSON for APIs and automation, CSV for spreadsheets, plain text for documentation.
When You Need A Record Lookup
Common scenarios where checking A records is essential
DNS Troubleshooting
Verify a domain points to the correct IP address after DNS changes. If your site shows the wrong content, an A record lookup confirms whether the IP is correct or still pointing to the old server.
Hosting Migration
Moving to a new server? Check A records to confirm the domain now points to your new server's IP. Combine with DNS Checker to monitor propagation across global DNS servers.
CDN Verification
Confirm your domain is using CDN edge IPs (Cloudflare, Akamai, CloudFront). CDN-enabled domains typically show multiple A records in different IP ranges corresponding to edge locations.
Security Analysis
Verify a domain points to expected hosting infrastructure. Detect potential DNS hijacking by comparing current A records against known-good IPs. Investigate suspicious domains during security audits.
How A Records Work
Understanding A records is fundamental to managing websites, troubleshooting DNS issues, and configuring hosting.
A Record vs CNAME
A records point directly to an IPv4 address (e.g., 93.184.216.34), while CNAME records point to another domain name (an alias). You cannot have both a CNAME and other record types at the same hostname. Use A records for your root domain (example.com) and CNAMEs for subdomains like www. Major difference: A records don't follow updates to the target IP, while CNAMEs automatically inherit changes from the canonical name.
A Record vs AAAA Record
A records store IPv4 addresses (32-bit, like 93.184.216.34), while AAAA records store IPv6 addresses (128-bit, like 2606:2800:220:1:248:1893:25c8:1946). Modern websites should have both for full internet connectivity. IPv6 adoption is growing, especially in mobile networks and newer infrastructure. Our tool shows both via tabs.
Multiple A Records & Load Balancing
Domains can have multiple A records pointing to different IPs. DNS servers often return them in round-robin order, distributing traffic across servers. This provides: load balancing (spread requests), redundancy (failover if one IP fails), and geographic distribution (CDNs). Google.com, for example, has 10+ A records across different data centers.
A Record TTL Best Practices
TTL determines how long DNS resolvers cache your A record. High TTL (24-48 hours) reduces DNS queries but slows propagation. Low TTL (5-15 minutes) enables faster changes but increases DNS load. Best practice: Use high TTL normally, lower it 24-48 hours before planned changes, then raise it again after propagation. Our tool shows TTL in human-readable format.
A Record Lookup Specifications
- Record Types
- A (default), AAAA, MX, CNAME, TXT, NS, SOA, CAA
- IP Format
- IPv4 dotted-decimal (e.g., 93.184.216.34)
- Multiple Records
- Shows all A records for load-balanced domains
- TTL Display
- Human-readable (5m, 1h, 24h) + seconds
- DNSSEC Detection
- DNSKEY and DS record checking
- Response Time
- < 500ms (cached: < 50ms)
- Cache Duration
- 5 minutes (300 seconds)
- Export Formats
- JSON, CSV, Plain Text
- API Access
- REST API at /api/v1/dns-lookup
Frequently Asked Questions
What is an A record in DNS?
An A record (Address record) is the most fundamental DNS record type. It maps a domain name like 'example.com' to an IPv4 address like '93.184.216.34'. When you type a domain in your browser, DNS servers use A records to find the IP address of the server hosting the website. Every publicly accessible website needs at least one A record.
What is the difference between an A record and a CNAME?
A records point directly to an IPv4 address (e.g., 93.184.216.34), while CNAME records point to another domain name (an alias). A records are used for the root domain (example.com), while CNAMEs are common for subdomains (www.example.com → example.com). You cannot have a CNAME and other records at the same hostname. If you need an IP address, you must use an A record.
Can a domain have multiple A records?
Yes, and it's common for high-traffic sites. Multiple A records enable load balancing (distribute traffic across servers), redundancy (failover if one server fails), and geographic distribution (CDNs). DNS servers may return A records in round-robin order to spread traffic. Google.com, for example, has over 10 A records.
How long does an A record take to propagate?
A record propagation typically takes 1-48 hours depending on the previous TTL value. If the TTL was 24 hours, some DNS servers will cache the old IP for up to 24 hours. To speed up propagation, lower the TTL to 5-15 minutes 24-48 hours BEFORE making changes. Use our DNS Checker to monitor propagation globally.
What should my A record point to?
Your A record should point to your web server's IPv4 address. This could be: a dedicated server IP, a cloud instance IP (AWS EC2, Google Cloud, Azure VM), a load balancer IP, or a CDN edge IP if using Cloudflare, Akamai, etc. Your hosting provider supplies this IP address in their documentation or control panel.
How do I check if my A record is correct?
Enter your domain in our A Record Lookup tool. Compare the returned IPv4 address to your expected server IP. If they don't match after a recent change, the old record may still be cached—use our DNS Checker to see propagation status across global servers. Also verify you edited the correct DNS zone (some domains have multiple).
What is TTL in A records?
TTL (Time To Live) tells DNS resolvers how long to cache the A record before checking for updates. Lower TTL (300-900 seconds) means faster propagation of changes but more DNS queries. Higher TTL (3600-86400 seconds) reduces DNS load but slows propagation. We display TTL in human-readable format: '5m' = 5 minutes, '1h' = 1 hour, '24h' = 24 hours.
Can an A record point to another domain?
No. A records can only point to IPv4 addresses, not domain names. To point to another domain, use a CNAME record instead. However, CNAME records cannot be used at the zone apex (naked domain like example.com)—only subdomains. For apex domains that need to point to another service, use ALIAS/ANAME records (if your DNS provider supports them) or a redirect.
What is the difference between A and AAAA records?
A records store IPv4 addresses (32-bit, format: 93.184.216.34), while AAAA records store IPv6 addresses (128-bit, format: 2606:2800:220:1:248:1893:25c8:1946). The 'AAAA' name comes from being four times the size of an 'A' record. Modern domains should have both for full internet connectivity, especially as IPv6 adoption grows on mobile networks.
Why is my A record not working?
Common causes: 1) Propagation not complete—wait up to 48 hours or check with DNS Checker. 2) Typo in the IP address. 3) A conflicting CNAME record at the same hostname. 4) DNS cache on your device—try flushing local DNS. 5) Edited the wrong DNS zone. 6) Registrar DNS vs hosting DNS conflict. 7) Server firewall blocking connections to the IP.
Check Any Domain's A Records Now
Enter a domain above to find IPv4 addresses, TTL values, and DNSSEC status. Free, fast, no registration required.
Try Another Lookup