IP/DNS Lookup

Supports internationalized domains, subdomains, website URLs and public IPv4 / IPv6. Enter a domain for DNS and WHOIS, or an IP for IP WHOIS and reverse DNS (PTR).

SPF Check

Check the SPF policy in TXT records, duplicates and common configuration issues.

Use the domain after @ in the sender address, without www.

SPF has not been queried.

DKIM Check

Look up the DKIM public key by domain and selector, checking format, revocation and RSA key size.

Use the selector from your mail provider. cPanel normally uses default; check the DKIM record name under Email Deliverability.

DKIM has not been queried. Selectors are not guessed automatically.

DNS results come from Cloudflare 1.1.1.1 and may be cached. IP WHOIS data comes from Internet registries and does not indicate the physical server location. Lookups do not change your DNS settings.

What do DNS and WHOIS lookups show?

A domain report shows addresses, domain WHOIS, IP WHOIS and nameserver, A, CNAME, MX and TXT records. Enter an IP directly for network registration and PTR reverse DNS, useful for checking routing before a migration or investigating connectivity.

1. Website and email routing

  • nameservers / NS:Lists nameservers for the domain. DNS records are usually managed at the corresponding DNS hosting service.
  • A / MX / TXT / CNAME:A lists IPv4 addresses and MX specifies mail servers. TXT commonly holds domain verification or mail policies; CNAME points a name to another hostname. Results show record values for easy comparison.

2. Public domain and IP registration

  • Domain Whois:Shows available registrar, dates, status and nameservers. Personal details may be redacted; a failed lookup does not prove the domain is unregistered.
  • Network Whois:Look up A-record IPs or enter a public IPv4 / IPv6 directly to view network ranges, organizations and registries. Missing country data is explicitly marked. Registration country is not the physical server location, and PTR is not a list of all websites on the IP.

3. SPF and DKIM mail authentication

  • SPF / DKIM:Run the two checks separately. SPF inspects the sending domain’s TXT policy; DKIM needs a signing domain and selector to inspect its public key. Valid DNS settings do not guarantee email delivery.

What should I check in DNS before moving a website?

Before moving, record nameservers, A, MX, TXT and CNAME entries and identify the services they point to. Test the new hosting before switching DNS and allow for cached records to update. Share your domain, website software, data size and email needs with ServerZoo to assess the migration and hosting plan.

What do SPF, DKIM and WHOIS tell you?

SPF and DKIM help receivers authenticate mail. Use the separate checks here and enter your mail provider’s DKIM selector. WHOIS shows public registration data; with a CDN, A records and IP WHOIS may identify the CDN rather than the origin host.

DNS, WHOIS and mail verification FAQ

Review eligibility, usage and responsibilities before taking the next step.

Why does a DNS lookup still show old records after an update?

Changes to DNS records may not appear worldwide immediately. After changing DNS settings, please allow approximately 24-48 hours for propagation. If you are only changing where an A record points, please allow approximately 4-8 hours for propagation before checking the results. If a lookup still returns the old records after the propagation period, first confirm which nameservers the domain currently uses, check that the changes were made on the correct DNS management platform, and verify the domain name and record type being queried. You can use ServerZoo’s DNS lookup tool to view the currently published A, MX, TXT, and other DNS records and help verify the DNS resolution status of your website, business email, and other online services.

Discuss your needs with support

Does the country in IP WHOIS identify the physical datacenter?

Not necessarily. It can come from the network’s country field or the registered organization’s address. That is registration data, not proof of the server’s location.

With a CDN or proxy, the IP may also identify an intermediary. Confirm hosting details and actual connectivity when choosing a location.

What should I enter for the DKIM selector? Does passing the check guarantee email delivery?

A DKIM selector is the name a mail hosting provider uses to identify a DKIM public key record. You can usually find it in the configuration details provided by your mail hosting provider. For example, if the DKIM record name is selector1._domainkey.example.com, the selector you need to enter is selector1. Use the selector supplied by your mail hosting provider for the lookup. The IP/DNS lookup tool does not automatically guess the selector. Separate lookup functions are available for DNS records, SPF validation, and DKIM validation. Please note that passing a DKIM check does not guarantee that every email will be delivered successfully. Whether an email is accepted or classified as spam may also depend on SPF, DMARC, the sending server's reputation, email content, and the recipient's filtering policies.

Discuss your needs with support

What are A, CNAME, MX, and TXT records used for?

Different types of DNS records handle settings for website connections, email, and other network services. A record: Points a domain or hostname to a specified IPv4 address, commonly used for website hosting configuration. CNAME record: Sets a hostname as an alias for another domain name, commonly used for subdomains or third-party services. MX record: Specifies the mail server that receives email for a domain. TXT records: Store text data and are commonly used for domain ownership verification, SPF, DKIM, DMARC, and other settings. If your website loads normally but you cannot receive email, checking the A record alone is not enough. You also need to verify that the MX and related TXT records are correct according to the settings provided by your email hosting provider.

How do nameservers differ from an A record?

Although nameservers and A records are both related to DNS, they serve different purposes. Nameservers determine which set of DNS servers provides resolution data for a domain, while A records map a specific domain or hostname to an IPv4 address. For example, after you set your domain's nameservers to the DNS servers provided by ServerZoo, you need to configure the relevant DNS records in ServerZoo's DNS management interface. Changing an A record on another DNS management platform that is not in use will not change or affect the resolution results currently served to the public. Before changing DNS records, we therefore recommend checking which nameservers your domain actually uses, then making your changes in the correct DNS server management platform.

Explore DNS hosting

If a WHOIS lookup returns no results, does that mean the domain is unregistered?

Not necessarily. If a WHOIS lookup returns no information, it does not mean the domain is available for registration. Registration details for some domains may be protected by privacy services or restricted under the registry’s public data disclosure policies. A WHOIS lookup service may also fail to return complete results because of connection issues, query limits, or temporary unavailability. WHOIS is primarily used to look up domain registration information and serves a different purpose from DNS record lookups. To check whether a domain is available for purchase, use the domain registration lookup and refer to the availability status provided by the domain registrar.

View domain registration

Should I enter a website URL or an email address for an SPF lookup?

When using the SPF lookup function, enter the sending domain you want to check, not a full email address or website URL. For example, to look up the SPF record for the domain used by sales@example.com, enter example.com without www, https:// or the full email address. The SPF Lookup Tool primarily checks publicly available SPF policies in DNS. It does not send test emails or directly verify the delivery outcome of a specific email.

Can I share DNS lookup results with support via a URL?

Yes. After completing a lookup with the ServerZoo DNS Lookup Tool, you can copy the results URL containing the domain name or IP address and share it with support for reference. When the recipient opens the shared link, they can run a new lookup for the same domain or IP address, making it easier for both parties to verify DNS resolution and related network information. Please note that the shared URL does not preserve the original lookup results. The system performs a new lookup using the data available when the link is opened, and may also use briefly cached data, so results may vary depending on when they are viewed. If you need to provide a record of a website outage or DNS issue at the time it occurred, we recommend including a screenshot of the lookup results and the time of the incident to help support compare the information and assess the issue.

Topics IP and DNS lookup

Choosing and using this service

For websites using a CDN, the IP address returned may not be the actual hosting server's IP address.

If a website uses a CDN or reverse proxy service such as Cloudflare, the IP address returned by a DNS lookup may belong to a CDN node rather than the server that actually hosts the website. DNS lookup results alone therefore cannot determine the hosting server’s actual location or connection performance. Businesses planning to purchase shared hosting or switch hosting providers should evaluate the data center locations, server specifications, and actual services offered by the provider, rather than deciding solely on the IP address returned by a lookup.

A website failing to load does not necessarily mean its DNS settings are incorrect

When a website cannot be accessed normally, DNS settings are just one of the things to check. Even if the domain correctly points to the website’s hosting server, problems with the SSL certificate, web server, or website application may still prevent visitors from browsing the site. Start with a DNS lookup to verify the domain’s resolution results. Then, based on the actual error message, use an HTTP header checker or SSL certificate checker to help identify where the problem lies. Distinguishing between DNS resolution, HTTPS connection, and website application issues helps you find the right solution and avoid repeatedly changing DNS settings that are already working correctly. Use the HTTP Header Checker

↑