An A (Address) record maps a domain name to an IPv4 address, telling browsers and other clients which server to connect to. It is one of the most fundamental DNS records and is what makes a domain reachable on the internet.

How do I use this A record lookup tool?

Enter a domain name (for example example.com) and run the lookup; the tool queries the domain's A record server-side and shows the IPv4 address or addresses it returns. Nothing you enter is stored, and no signup is required.

Why does an A record matter?

Without a correct A record, visitors typing your domain cannot reach your website or service because there is no IPv4 address to connect to. Checking it confirms your domain points to the right server, which is essential after moving hosts or changing IPs.

How do I read the result and fix a wrong one?

Compare the returned IPv4 address to the address your hosting provider assigned; if they do not match, update the A record in your DNS provider's control panel. Multiple addresses simply mean the domain is served from several servers for redundancy or load balancing.

Why might the result be old or missing?

DNS results are cached according to the record's TTL, so a recent change may not appear until the old value expires, sometimes hours later. If no A record is returned, the domain may only use an IPv6 (AAAA) record, a CNAME, or may have no address configured at all.

A Record Look Up

Related tools

Domain name

What do you want to look up?

Blacklist Look Up

Looks up whether this domain's IP address (or the IP address you entered) appears on common email blacklists (DNSBL) — being listed can cause outgoing mail to be rejected or sent to spam.

Also look up blacklist status when I run this search

What this is

The A record maps a domain name to an IPv4 address. It is the most fundamental DNS record: when someone visits your website, their browser resolves the domain to the IPv4 address in the A record and connects there.

How to read your result

A healthy result shows one or more IPv4 addresses. Multiple addresses are normal for load-balanced sites. Verify the address actually belongs to your current hosting provider — an old address that still resolves is the most common surprise.

Common problems and how to fix them

No A record exists

How it shows up: The website is unreachable by name; browsers show "server not found" even though the server itself is running fine.

How to fix it: Add an A record at your DNS provider pointing to your web server's public IPv4 address. If the site should only run on www, add the A record on www and consider a redirect from the bare domain.

A record points to the old server after a migration

How it shows up: Some or all visitors still land on the old host; changes you deploy never show up for them.

How to fix it: Update the A record to the new IP at the DNS provider that is actually authoritative (check the NS records to confirm which one that is). Lower the TTL before future migrations so changes propagate faster.

Record updated but visitors still see the old site

How it shows up: You changed the A record but some networks keep resolving the old IP for hours.

How to fix it: This is TTL caching, not an error. Resolvers keep the old answer until the TTL expires. Wait out the previous TTL, and set a lower TTL (e.g. 300 seconds) ahead of planned changes next time.

Frequently asked questions

What is an A record?: An A (Address) record maps a domain name to an IPv4 address, telling browsers and other clients which server to connect to. It is one of the most fundamental DNS records and is what makes a domain reachable on the internet.
How do I use this A record lookup tool?: Enter a domain name (for example example.com) and run the lookup; the tool queries the domain's A record server-side and shows the IPv4 address or addresses it returns. Nothing you enter is stored, and no signup is required.
Why does an A record matter?: Without a correct A record, visitors typing your domain cannot reach your website or service because there is no IPv4 address to connect to. Checking it confirms your domain points to the right server, which is essential after moving hosts or changing IPs.
How do I read the result and fix a wrong one?: Compare the returned IPv4 address to the address your hosting provider assigned; if they do not match, update the A record in your DNS provider's control panel. Multiple addresses simply mean the domain is served from several servers for redundancy or load balancing.
Why might the result be old or missing?: DNS results are cached according to the record's TTL, so a recent change may not appear until the old value expires, sometimes hours later. If no A record is returned, the domain may only use an IPv6 (AAAA) record, a CNAME, or may have no address configured at all.