DNS Tools

A Record Lookup

Look up a domain's A records - the IPv4 addresses it points to.

Enter a domain to look up its A records (IPv4 addresses).

More DNS Tools

DNS Lookup AAAA Record Lookup TTL Checker MX Record Lookup DNSSEC Checker TXT Record Lookup SRV Record Lookup CNAME Lookup

JustChecker tracks your DNS records continuously and alerts you the moment something changes.

What Is an A Record?

An A (Address) record connects a domain name to an IPv4 address such as 93.184.216.34. When someone opens your website, their browser uses the A record to find the server. This tool shows every A record for a domain and its TTL.

When to Use It

After pointing a domain to a new host or server.
When a site loads the old server after a migration.
To check which IP a subdomain such as api.example.com resolves to.

How to Use It

Enter the domain or subdomain.
Compare the returned IP addresses with the IP your hosting provider gave you.

Understanding the Result

Several A records mean traffic is spread across several servers. The TTL shows, in seconds, how long resolvers may cache the answer - after a change, some visitors may see the old IP until that time has passed.

Limitations

If the domain uses a CDN such as Cloudflare, you will see the CDN's IPs, not your origin server's. For IPv6 addresses use the AAAA Record Lookup.

Frequently Asked Questions

An A ("Address") record maps a hostname to an IPv4 address - it's the record that tells a visitor's browser exactly which server to connect to when they type your domain.

Multiple A records are commonly used for load balancing or redundancy across several servers, or because a CDN provider publishes several edge IP addresses for the same hostname.

If you're behind a CDN or reverse proxy (Cloudflare, for example), the A record often points to the CDN's IP address rather than your origin server's actual IP - this is expected and intentional in that setup.

A lower TTL (e.g. 300 seconds) makes future changes propagate faster but increases DNS query volume slightly; a higher TTL (e.g. 3600+ seconds) reduces query load but means changes take longer to take effect globally - most sites use something in between unless actively planning a migration.

Technically yes, but a public-facing A record pointing at a private (RFC 1918) IP address would be unreachable from the public internet - this is almost always a misconfiguration for a production website.

When you specifically need to confirm or troubleshoot IPv4 resolution - for example, verifying a server migration actually took effect - a focused, single-record-type view is faster to read than a combined multi-record report.

An A record maps to an IPv4 address; an AAAA record maps the same kind of hostname-to-address relationship, but to a (longer) IPv6 address instead.