A Record Lookup

Use the A Record Lookup tool on IPMYP to check which IPv4 address a domain or subdomain points to. If you have changed your hosting provider, updated your DNS settings, moved a website to a new server, or want to confirm the real destination IP of a domain, this tool helps you verify the DNS A record online in seconds.

An A record is one of the most important DNS records because it connects a domain name to an IPv4 address. With IPMYP, you can enter a domain such as example.com or a subdomain such as www.example.com and instantly see the IPv4 address and related DNS details returned for that hostname.

If you first want to see the IP address of your own current connection, you can check your public IP address before testing DNS records for a domain.

What Is an A Record?

An A record, also known as an Address record, is a DNS record that maps a domain or subdomain to an IPv4 address. When someone types a website address into a browser, DNS uses records like the A record to find the server that should receive the request.

For example, if example.com has an A record pointing to 203.0.113.10, browsers and other clients know that requests for that domain should be sent to that IPv4 address.

A records are commonly used for:

• Connecting a root domain, such as example.com, to a web server.
• Pointing subdomains such as app.example.com, panel.example.com, or shop.example.com to different servers.
• Configuring hosting, cloud servers, load balancers, and CDN-related DNS setups.
• Verifying whether a domain still points to an old server or has moved to a new IP address.

If the A record is wrong, outdated, missing, or cached incorrectly, users may be sent to the wrong server or the website may fail to load.

How to Use the A Record Lookup Tool

Using the IPMYP A Record Lookup tool is simple. You do not need to install command-line tools or use terminal commands.

1. Enter a domain name or subdomain, such as example.com or www.example.com.
2. Run the A record check.
3. IPMYP sends a DNS query for the hostname you entered.
4. Review the result, including the IPv4 address, record type, hostname, and TTL when available.
5. Use the result to confirm whether the domain points to the correct server.

For a broader DNS check that includes MX, TXT, NS, CNAME, SOA, WHOIS, Ping, SSL, and other checks, use the main DNS lookup tool and online network tools hub.

What Information Does an A Record Report Show?

After running the check, the A record report may show several important DNS details.

• Host: The domain or subdomain being checked.
• Type: The DNS record type, which should be A.
• IP Address: The IPv4 address connected to the domain, such as 203.0.113.10.
• TTL: The Time To Live value that tells DNS resolvers how long they may cache the record.

If a domain has multiple A records, the tool may show more than one IPv4 address. This can happen with load balancing, multiple web servers, cloud hosting, or high-availability infrastructure.

When Should You Check a DNS A Record?

A record lookup is useful whenever you need to confirm where a domain or subdomain actually points. It is especially helpful after DNS changes, hosting migrations, server updates, and troubleshooting website access issues.

After Changing Hosting or Server IP

When you move a website to a new host or change the server IP address, the A record must point to the new IPv4 address. Checking the A record helps you confirm whether the DNS update has been applied correctly.

When a Website Does Not Load

If a website is not opening, one possible reason is that the domain is pointing to the wrong IP address. An A record check helps you verify whether the DNS configuration is sending users to the correct server.

When Testing Subdomains

Different subdomains can point to different servers. For example, your main website, app, dashboard, API, and staging environment may each use separate A records. This tool helps you check each hostname individually.

When Verifying CDN or Proxy Setup

If you use a CDN, cloud security service, reverse proxy, or load balancer, the A record may point to that provider instead of your origin server. This is normal, but checking the A record helps you understand what IP address is publicly visible in DNS.

A Record vs AAAA Record

An A record points a domain to an IPv4 address. An AAAA record points a domain to an IPv6 address. Both records are used to connect domain names to IP addresses, but they work with different IP versions.

If your website supports IPv6, you may also want to check its AAAA record. If your domain only uses IPv4, the A record is usually the main DNS record responsible for connecting the domain to the web server.

A Record vs CNAME Record

An A record points a domain or subdomain directly to an IPv4 address. A CNAME record points one hostname to another hostname instead of pointing directly to an IP address.

For example, a root domain often uses an A record, while a subdomain such as www.example.com may use a CNAME record to point to another hostname. The best option depends on your DNS provider, hosting setup, CDN, and application architecture.

Why Does the A Record Show a Different IP Than My Hosting Account?

The IP address shown in an A record may be different from the origin server IP if you use a CDN, reverse proxy, cloud firewall, DDoS protection service, or managed hosting platform. In those cases, the public DNS record may point to the provider’s edge or proxy IP instead of your real backend server.

This is common with modern hosting and CDN setups. The important question is whether the visible A record matches the IP address or service endpoint your DNS provider or hosting provider instructed you to use.

How Long Do A Record Changes Take?

A record changes may appear quickly, but full visibility across the internet depends on DNS caching and the TTL value. Some resolvers may update within minutes, while others may keep older records for longer.

If you recently changed an A record, you may temporarily see different results from different networks or DNS resolvers. This does not always mean the change failed; it may simply mean that cached DNS data is still being used.

Common Use Cases for A Record Lookup

• Website migration: Confirm that a domain points to the new server IP after moving hosting.
• DNS troubleshooting: Check whether a domain is resolving to the expected IPv4 address.
• Subdomain management: Verify that app, API, panel, shop, or staging subdomains point to the correct servers.
• CDN verification: Check whether DNS points to a CDN or proxy provider.
• Server audits: Review which IP addresses are publicly connected to important domains.
• Downtime investigation: Identify DNS misconfiguration as a possible cause of website access problems.

Best Practices for Managing A Records

• Always confirm the correct IPv4 address before changing an A record.
• Lower TTL before planned migrations when possible, then raise it again after the change is stable.
• Check both root domain and important subdomains after DNS updates.
• Document old and new IP addresses during hosting migrations.
• Be careful when editing DNS records used by production websites, APIs, mail systems, or customer dashboards.
• Remember that CDN or proxy services may intentionally hide your real origin IP.

Frequently Asked Questions

What does an A Record Lookup do?

An A Record Lookup checks the DNS A record of a domain or subdomain and shows the IPv4 address connected to it. This helps you confirm where the domain points on the internet.

What is a DNS A record?

A DNS A record is a record that maps a domain name to an IPv4 address. It is commonly used to connect websites and subdomains to web servers.

Can a domain have multiple A records?

Yes. A domain can have multiple A records. This may be used for load balancing, redundancy, cloud hosting, or multi-server infrastructure.

Why is my A record not updating?

Your A record may not appear updated everywhere because of DNS caching, TTL values, resolver behavior, or propagation delay. Wait for the TTL period and check again from different networks if needed.

What is the difference between A and AAAA records?

An A record points to an IPv4 address, while an AAAA record points to an IPv6 address. Websites can use one or both depending on their hosting and network configuration.

What is the difference between A and CNAME records?

An A record points directly to an IP address. A CNAME record points one hostname to another hostname. CNAME is often used for subdomains, while A records are commonly used for root domains and direct IPv4 mapping.

Can I use an A record for a subdomain?

Yes. You can create an A record for subdomains such as app.example.com, api.example.com, or panel.example.com and point each one to a specific IPv4 address.

Why does my A record show a CDN IP?

If you use a CDN, proxy, or cloud security service, your public A record may show the provider’s IP address instead of your origin server IP. This is expected in many CDN and reverse proxy setups.

Check A Record Online With IPMYP

IPMYP’s A Record Lookup tool gives you a fast way to check the IPv4 address connected to any domain or subdomain. Enter a hostname above, run the check, and review the DNS A record result to confirm where your domain points.