A website or subdomain should point to an IPv4 address and you need to confirm the live DNS answer.
A Record Lookup
Check live IPv4 A records for a domain or hostname.
Use A Record Lookup to inspect the public IPv4 addresses currently returned for a hostname, compare them with the address you expected to publish, and decide what to check next if the answer looks wrong.
Check A records before moving to propagation, nameserver, or website troubleshooting.
Lookup result
example.com
NOERROR
Type Value TTL
No A records were returned for this hostname by the resolver.
What this A Record Lookup tool does
A Record Lookup queries the public A records for a domain or hostname and returns the IPv4 answers currently visible from the resolver used by this page.
Use it to confirm whether a hostname resolves over IPv4, inspect the returned addresses, and compare the live answer with the configuration you intended to publish.
It does not confirm whether the website or service behind that IPv4 address is healthy. It only confirms the DNS A-record layer.
When to use this tool
A record was changed recently and you want to see whether public DNS is returning the new IPv4 target.
A hostname resolves inconsistently between networks and you need a fast first A-record check.
A site is behind a CDN or proxy and you want to confirm which public IPv4 addresses are being returned.
A migration is in progress and you need to compare the live A record with the address you intended to publish.
You want a focused IPv4 lookup before moving to propagation, nameserver, or service-level checks.
How to use A Record Lookup
- Enter the domain or hostname you want to check.
- Run the lookup to request public IPv4 A answers from a recursive resolver.
- Review the returned IPv4 address or addresses, TTL, and response status.
- Compare the live result with the A record you expected to publish.
- If the result is wrong or missing, continue to nameserver, propagation, or service checks.
How to interpret A record results
A record found
Likely meaning: Public DNS returned one or more IPv4 addresses for the hostname.
Common causes: This usually means the hostname resolves publicly over IPv4 from the resolver used by this page.
Next action: Compare the returned address or addresses with the target you intended to publish.
No A record found
Likely meaning: The hostname exists, but no IPv4 A record was returned.
Common causes: The host may only have AAAA or CNAME data, the A record may be missing, or the name may be published in the wrong zone.
Next action: Check DNS Lookup for other record types, then verify nameservers and propagation.
Unexpected IPv4 address
Likely meaning: The lookup returned IPv4 addresses, but not the ones you expected.
Common causes: Common causes are stale DNS, edits in the wrong provider, partial migration, CDN or proxy edge IPs, or old records left in place.
Next action: Compare the live answer with your DNS provider configuration, then check propagation or proxy settings.
Multiple A records returned
Likely meaning: More than one IPv4 address exists for the same hostname.
Common causes: This may be normal for load balancing, failover, or proxy/CDN behavior, but it can also reveal stale or conflicting records.
Next action: Confirm whether multiple public IPv4 answers are expected. If not, remove outdated or conflicting records.
NXDOMAIN
Likely meaning: The queried hostname does not exist in public DNS.
Common causes: Typos, missing subdomains, unpublished records, or the wrong zone are common causes.
Next action: Verify the exact hostname, then check nameservers and the zone where the record was created.
SERVFAIL
Likely meaning: The recursive resolver could not complete the lookup successfully.
Common causes: This often points to DNSSEC failure, broken delegation, or upstream nameserver issues.
Next action: Run NS Lookup and DNSSEC Check next, then compare with propagation results.
Common DNS issues this tool helps uncover
A record published in the wrong DNS provider or wrong zone
Public DNS still returning an old IPv4 address after a migration
CDN or reverse-proxy edge IPs being returned instead of the origin server
The hostname only has AAAA or CNAME data and no direct A record
Nameserver delegation mismatch after DNS changes
Resolver differences during propagation or caching windows
Split-horizon DNS where internal and public IPv4 answers differ
Next steps after A Record Lookup
Check DNS propagation
If you changed the A record recently, compare how recursive resolvers are seeing it.
Verify nameservers
Use NS Lookup if the live A record looks wrong and you need to confirm which provider is authoritative.
Inspect other DNS records
If no A record appears, check for AAAA, CNAME, or other related DNS answers.
Move to service checks
If the A record looks correct, continue to Ping, HTTP Check, or HTTPS Check.
Related tools
DNS Lookup
Query A, AAAA, CNAME, TXT, and other DNS records for a domain.
DNS Propagation Check
Verify whether recent DNS changes are visible across resolvers.
NS Lookup
Check authoritative name servers and delegation for a domain.
Ping
Check whether a host responds and measure round-trip latency.
HTTP Check
Review HTTP response status, headers, and redirect behavior.
HTTPS Check
Verify HTTPS availability, response chain, and TLS handshake basics.
A Record Lookup FAQ
What does A Record Lookup check?
It checks the live public A records for a domain or hostname and returns the IPv4 answers currently visible from the resolver used by the page.
What input should I enter?
Enter a domain or hostname such as example.com, app.example.com, or www.example.com. Do not enter a full URL.
Why does the result show Cloudflare or CDN IPs instead of my server IP?
If the hostname is proxied through a CDN or reverse proxy, public A records often point to the edge service instead of the origin server.
Why are multiple A records returned?
Multiple A records can be normal for load balancing, failover, or proxy networks, but they can also indicate stale or duplicated records.
What should I check after A Record Lookup?
Usually DNS propagation, nameservers, and then service-level checks like Ping, HTTP Check, or HTTPS Check.
How is A Record Lookup different from DNS Lookup?
A Record Lookup is focused only on IPv4 A answers. DNS Lookup is broader and can inspect A, AAAA, MX, TXT, NS, CNAME, and other record types.