What Is an A Record?

An A record is one of the most important entries in DNS (Domain Name System). It maps a domain name to an IPv4 address so browsers and apps know which server to contact. If you are learning domain lookup basics on WhoisSEO, understanding A records is essential — they are often the first record you check after a WHOIS query when a website will not load.

A record definition (in plain language)

The letter A stands for Address. An A record answers: “What IPv4 address should this hostname use?”

• Hostname — the name in DNS, such as example.com or www.example.com.
• IPv4 address — four numbers separated by dots, for example 93.184.216.34.
• TTL (Time to Live) — how long resolvers cache the answer before asking again.

Without a correct A record (or an equivalent alias via CNAME), a domain name may not resolve to a website even if registration in WHOIS looks healthy.

How an A record works

1. A user types a domain name into a browser.
2. The device asks a DNS resolver for the A record of that hostname.
3. The resolver walks the DNS hierarchy (root → TLD → authoritative nameserver).
4. The authoritative server returns the A record with an IPv4 address.
5. The browser connects to that IP and requests the web page.

You can inspect live records with DNS Lookup on WhoisSEO. For registration details (registrar, expiry, nameservers), use WHOIS Lookup first, then DNS for routing.

A record vs AAAA record

Both map names to addresses, but they target different IP versions:

• A record → IPv4 (example: 192.0.2.1).
• AAAA record → IPv6 (longer hexadecimal addresses).

Many sites publish both so they work on IPv4-only and IPv6-ready networks. If a site loads for some users but not others, compare A and AAAA records — a missing or wrong AAAA record can affect IPv6 clients while A still works on IPv4.

Common A record examples

Hostname	Type	Value	Purpose
example.com	A	203.0.113.10	Root domain website
www.example.com	A	203.0.113.10	WWW subdomain (same server)
api.example.com	A	203.0.113.20	Separate API server

Some setups use a CNAME for www instead of a separate A record. You cannot place a CNAME on the zone apex (example.com) in classic DNS — that is why apex domains often use A or ALIAS/ANAME solutions from DNS providers.

Where A records fit in DNS setup

A records are usually created at your DNS host (the service listed as nameservers in WHOIS). A typical flow:

1. Register the domain name with a registrar.
2. Point nameservers to your DNS provider or host.
3. Add an A record pointing the hostname to your server’s public IPv4.
4. Set TTL (300–3600 seconds is common during changes; higher when stable).

For the full setup sequence, see How DNS setup works. For email routing (different record type), read What is an MX record?.

How to check A records (domain lookup workflow)

1. WHOIS — confirm the domain is active and note nameservers. Tool: WHOIS Lookup.
2. DNS — query A (and AAAA) for the hostname you care about. Tool: DNS Lookup.
3. Compare — does the IP match your hosting panel? If not, DNS may be stale, wrong zone, or cached.
4. Wait for TTL — after changes, old A records can persist until TTL expires.

This domain lookup pattern — whois then dns — is the standard troubleshooting path on WhoisSEO.

Common mistakes and fixes

• Wrong IP in the A record — site points to an old server. Update the A value at your DNS host.
• A record only on www, not apex — www works but bare domain fails. Add A (or redirect) for the apex.
• Conflicting CNAME and A — CNAME cannot coexist with other records on the same name (except DNSSEC).
• Ignoring TTL during migrations — plan lower TTL before a cutover, raise it after stability.
• Firewall allows wrong IP — DNS is correct but the server blocks traffic; A record alone does not fix hosting firewalls.

A records and security

A records are public. Anyone can look them up — that is by design. Security does not come from hiding the IP; it comes from patching servers, TLS certificates, WAFs, and access controls. When investigating unknown domains, A records help you see which network hosts the site (useful alongside reverse IP tools on WhoisSEO).

FAQ

• How many A records can one name have? Multiple A records are allowed (DNS round robin). All listed IPs may receive traffic.
• Does an A record handle email? No. Mail uses MX records. Websites use A or AAAA (or CNAME chains).
• How long until an A record change works? Up to the previous TTL worldwide; often minutes to a few hours.
• What if there is no A record? The hostname may not resolve for IPv4, or a CNAME may delegate the answer elsewhere.

Conclusion

An A record links a domain name to an IPv4 address — the foundation of most website DNS configuration. On WhoisSEO, run WHOIS Lookup for registration context, then DNS Lookup to read A records and complete your domain lookup. Pair this guide with How DNS setup works and What is an MX record? to cover the core record types every domain owner should know.