IPv4 addresses for a domain
DNS & Records
DNS Lookup Every DNS record for any domain A Record Lookup IPv4 addresses for a domain AAAA Record Lookup IPv6 addresses for a domain MX Lookup Mail servers for a domain NS Lookup Authoritative name servers TXT Lookup TXT records, SPF, verification CNAME Lookup Canonical name (alias) records SOA Lookup Start of Authority record SRV Lookup Service location records CAA Lookup Which CAs may issue certificates Reverse DNS (PTR) IP address to hostname DNSSEC Check Is the domain signed and validated? DNS Health Check A full delegation & DNS report cardEmail Deliverability
SPF Check Validate your Sender Policy Framework record DMARC Check Inspect and grade your DMARC policy DKIM Check Find and validate your DKIM public key Blacklist Check Check an IP against email blocklists (DNSBLs) SMTP Test Connect to a mail server and check STARTTLS MTA-STS Check Enforced TLS policy for inbound mail BIMI Check Brand logo record for email TLS-RPT Check SMTP TLS reporting policyNetwork & Web
SSL Certificate Check Inspect a site's TLS certificate and expiry HTTP Header Check Inspect response headers, redirects and security Ping (TCP) Reachability and latency over TCP Port Check Which common ports are openDomain
WHOIS Lookup Registration data for domains, IPs and ASNsAn A record maps a domain name to one or more IPv4 addresses. It is the most fundamental DNS record, the one that tells browsers and clients which server to connect to for a hostname. Without a valid A record, a domain will not resolve to a website over IPv4.
When you type a hostname, your resolver looks up its A record to find the IPv4 address to connect to. The record is a simple mapping, for example example.com to 93.184.216.34. A hostname can have several A records pointing to different IPs; resolvers hand them out in rotation, giving a basic form of load balancing. The A record's TTL controls how long resolvers cache the address before checking again, which matters when you move a site to a new server.
Each A record row shows a hostname, the IPv4 address it resolves to, and a TTL in seconds. A result like example.com A 93.184.216.34 TTL 3600 means the domain points to that IPv4 address and resolvers may cache it for one hour. If you see multiple A records for the same name, traffic is spread across those IPs. If the address does not match your hosting provider's server, your DNS still points at an old host and needs updating.
The most common issue is an A record pointing at an old IP after a hosting move, which sends visitors to the wrong or dead server. Fix it by updating the record at your DNS provider and waiting for the TTL to expire. A missing A record on the root domain (example.com) means the site loads at www but not the bare domain. Conflicts also arise when you try to add an A record to a name that already has a CNAME, which DNS does not allow on the same hostname.
An A record is a DNS record that maps a domain name to an IPv4 address, such as 93.184.216.34. It is what lets browsers connect to the correct server when someone visits your domain. The A stands for address. It is the most basic and essential record type, since without one a hostname cannot resolve over IPv4.
An A record points a hostname directly to an IPv4 address, while a CNAME points a hostname to another hostname whose A record is then used. Use an A record for a root domain or when you have a fixed IP; use a CNAME for subdomains that should follow a provider's hostname, such as a CDN or SaaS endpoint.
Yes, a domain can have multiple A records pointing to different IPv4 addresses. Resolvers return them in rotation, distributing requests across servers for basic load balancing and redundancy. If one address is unreachable, clients can retry another. This is common for large sites that run several front-end servers behind the same hostname.
Change an A record in your DNS provider's control panel by editing the record's IP address value and saving. The change takes effect once the old record's TTL expires, which can take from minutes to a day. Lower the TTL a day before the change so it propagates faster. IPeek caches its result for 15 minutes.
An A record may not resolve because it does not exist for that hostname, the domain's name servers are misconfigured, or the change has not finished propagating. Verify that your NS records at the registrar match your DNS provider, confirm the record exists for the exact hostname, and wait for the TTL to expire after any edit.