What is an A record?
An A record, short for Address Record, is a fundamental DNS (Domain Name System) entry that maps a domain name to its corresponding IPv4 address. It acts as the bridge between the human-readable domain name you type into a browser and the numerical IP address that computers use to locate servers on the internet.
When you visit a website, your browser contacts a DNS resolver, which looks up the A record for that domain and returns the associated IP address. Your browser then connects directly to that IP to load the site. The whole process happens in milliseconds, completely invisibly to the end user.
Why do A records matter?
Remembering that a website lives at an IP like 142.250.80.46 is impractical. A records solve this by letting you use easy-to-remember domain names instead. Behind the scenes, DNS translates every domain lookup into the IP address the network actually needs.
Beyond basic name resolution, A records are used for traffic distribution. A single domain can have multiple A records pointing to different IP addresses, allowing DNS-level load balancing where requests are spread across several servers. They are also used for failover configurations, where traffic automatically shifts to a backup server if the primary goes down.
How to use the A record lookup tool
Using this tool is straightforward. Enter the domain name you want to check in the search field — you can include or omit the www prefix, and there is no need to add https://. Click Lookup and the tool will query DNS in real time and return the results within seconds.
The results table shows three pieces of information for each record: the host or domain name, the IP address it resolves to, and the TTL (Time to Live) value. If multiple A records are returned, the domain is using multiple IP addresses — a common pattern for high-traffic sites.
Understanding the results
Each row in the results represents one A record. The Host column shows the fully qualified domain name. The IP Address column contains the IPv4 address the domain resolves to, which you can use to identify the server or hosting provider. The TTL value indicates how long, in seconds, this DNS record is cached before resolvers re-query the authoritative name server for a fresh value.
A short TTL (like 60 or 300 seconds) means DNS changes propagate quickly — useful during server migrations or outages. A longer TTL (like 3600 seconds or more) reduces DNS query load but means changes take longer to reach end users worldwide.
Frequently Asked Questions
What is the difference between an A record and a CNAME record?
An A record maps a domain name directly to an IPv4 address. A CNAME (Canonical Name) record instead maps one domain name to another domain name, which then has its own A record. For example, www.example.com might be a CNAME pointing to example.com, which in turn has an A record pointing to the server IP. CNAMEs are useful for aliasing subdomains without duplicating IP configuration, but they cannot be used at the root (apex) of a domain — only A records can sit at the domain root.
What is the difference between an A record and an AAAA record?
A records handle IPv4 addresses, which are 32-bit numerical addresses written in four groups (e.g., 192.168.1.1). AAAA records serve the same purpose but for IPv6 addresses, which are 128-bit and written in eight groups of hexadecimal values (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). Modern servers often have both record types configured to support clients using either protocol.
Why does a domain have multiple A records?
A domain can have multiple A records to distribute incoming traffic across several servers, a technique called DNS round-robin load balancing. When a DNS resolver returns multiple A records, the client typically tries them in order or at random, spreading the load. Multiple A records are also used for redundancy — if one IP becomes unreachable, clients can fall back to another. Large websites and CDN-backed services commonly use this pattern.
What does TTL mean in an A record?
TTL stands for Time to Live and represents the number of seconds that DNS resolvers and browsers should cache a record before fetching a fresh copy. A TTL of 3600 means the record is cached for one hour. After that time expires, resolvers will query the authoritative name server again for an updated value. Lowering the TTL before making DNS changes is a common best practice to minimize how long outdated records propagate after the change.
How long does it take for A record changes to take effect?
DNS changes propagate at a rate determined by the previous TTL value of the record being changed. If your A record had a TTL of 3600 seconds (one hour), it can take up to an hour for all DNS resolvers around the world to clear their cache and pick up the new value. In practice, propagation is often faster for many users, but full global propagation can take anywhere from a few minutes to 48 hours depending on TTL settings and resolver behavior.
Can I look up A records for subdomains?
Yes. You can look up A records for any fully qualified domain name, including subdomains like blog.example.com or shop.example.com. Simply enter the full subdomain in the search field. Each subdomain can have its own independent A record pointing to a different IP address, which is how many organizations host different services on separate servers under the same domain.