Web Hosting

Best DNS Check Tools: 20 Options for DNS Troubleshooting

By Afonso Macosso · November 17, 2026

Advertisement
Ad disclaimer: For links on this page, DESKING APP may earn a commission from the provider. This supports our work and has no influence on our editorial rating.
Best DNS Check Tools: 20 Options for DNS Troubleshooting
Advertisement
Table of contents
  1. 1. What are DNS Check Tools?
  2. 2. Why DNS checking matters
  3. 3. How DNS checking tools work
  4. 4. DNS records every administrator should understand
  5. 5. Important features to look for in a DNS checker
  6. 6. Comparison of the 20 Best DNS Check Tools
  7. 7. Detailed reviews of the 20 tools
  8. 7.1 General DNS lookup and record inspection
  9. 7.2 Domain research and DNS reconnaissance
  10. 7.3 DNS monitoring and performance
  11. 8. How to choose the right DNS checker
  12. 9. Practical DNS troubleshooting scenarios
  13. 10. A professional DNS troubleshooting workflow
  14. 11. Final verdict: which DNS check tool should you choose?
  15. Frequently Asked Questions

Every time someone visits a website, sends an email or connects to an online application, DNS plays a part in making that connection possible.

A domain name may look simple to a user, but behind it sits a distributed system of records, resolvers, authoritative name servers and caching mechanisms.

One incorrect record can send visitors to the wrong server, interrupt email delivery or make an application inaccessible.

The Best DNS Check Tools give administrators a practical way to inspect this system.

They help answer questions such as: Does the domain point to the correct IP address?

Are the new nameservers active?

Are email records configured properly?

Do DNSSEC signatures validate?

Are different resolvers returning different answers?

Has a critical DNS record changed without authorisation?

These questions matter during everyday website administration, but they become particularly important during hosting migrations, email deployments, domain transfers, security reviews and service outages.

A quick lookup can confirm a record, while a deeper DNS audit can expose problems in delegation, zone consistency or security configuration.

This guide reviews 20 DNS tools, from straightforward browser-based checkers to specialist diagnostic and monitoring services.

Each tool receives an individual assessment, including its main purpose, features, advantages, disadvantages and ideal use cases.

A comparison table also helps distinguish tools that may appear similar but solve different technical problems.

The aim is not simply to list websites that perform DNS lookups.

It is to help you understand what each tool can actually do, when it is worth using and where its limitations begin.

1. What are DNS Check Tools?

DNS Check Tools are utilities that query, inspect, analyse or monitor the Domain Name System.

They help users understand how a domain is configured and how DNS information is being returned by different servers.

The term covers several types of tools, and this distinction is important.

A DNS lookup tool may simply retrieve an A, MX or TXT record.

A DNS propagation checker compares responses from selected resolvers.

A DNS health checker examines the wider configuration of a zone.

A DNSSEC analyser investigates cryptographic signatures and delegation.

A monitoring service watches records or services over time.

These tools are used by different people for different reasons:

  • Website owners use them to confirm that a domain points to the correct hosting provider.
  • System administrators use them to diagnose nameserver, email and network configuration problems.
  • Developers use them to verify custom domains, application subdomains and service integrations.
  • Email administrators use them to inspect MX, SPF, DKIM and DMARC records.
  • Security professionals use them to examine DNSSEC, identify publicly visible hostnames and investigate suspicious changes.
  • Hosting providers use them to troubleshoot customer domains and validate DNS configurations.
  • Network engineers use them to assess resolver performance and investigate resolution failures.

A useful DNS checker should make the information easier to understand, but it cannot replace technical judgement.

A tool may report that an A record exists, for example, without confirming that the destination server is online.

Another may show that a DNSSEC record is present without proving that the entire validation chain is healthy.

The best approach is to understand what a particular test measures before using its result to make a production change.

2. Why DNS checking matters

DNS is often treated as a background service until something stops working.

That is a mistake.

A business domain can support a public website, email, cloud applications, remote access, customer portals and several internal services.

A DNS error can therefore affect more than one department.

Preventing website downtime

A website depends on DNS to direct visitors to the correct destination.

If an A record points to an old server, visitors may reach a previous hosting environment or receive an error.

This often happens during hosting migrations.

The new website may be fully operational, but the domain still points to the old IP address.

A DNS lookup identifies the published address, while a propagation checker helps compare responses from selected locations.

Protecting email delivery

Email depends on several DNS records.

MX records identify mail servers, while SPF, DKIM and DMARC support email authentication.

A missing or incorrect MX record can disrupt incoming messages.

An incomplete SPF policy or a missing DKIM record can affect authentication.

A DMARC policy that is too strict for the organisation's actual sending environment can cause legitimate messages to fail.

DNS checkers help administrators inspect these records and compare them with the values required by the email provider.

Making migrations safer

A domain migration may involve a new registrar, DNS provider, hosting company or email platform.

Each change introduces a possibility of misconfiguration.

A proper DNS review before a migration helps identify existing records that must be preserved.

A review after the migration helps confirm that the new authoritative servers publish the expected information.

This is particularly important when the DNS zone contains records for services that are not part of the website migration.

Removing an unfamiliar TXT, MX or CNAME record can disrupt an application even when the main website continues to work.

Improving security

DNS is part of the organisation's external attack surface.

DNSSEC helps validating resolvers verify the authenticity of DNS data.

CAA records allow domain owners to restrict which certificate authorities may issue certificates.

Monitoring can reveal unexpected changes to important records.

DNS reconnaissance tools can also help security teams understand which hostnames an organisation exposes publicly.

That information is useful for authorised asset discovery and security assessments.

Reducing troubleshooting time

Without DNS checks, administrators may spend time investigating the wrong system.

A website error might appear to be a hosting problem when the actual cause is an incorrect DNS record.

An email delivery issue might appear to be a mailbox problem when the MX record still points to the old provider.

A well-chosen checker helps establish whether DNS is actually responsible before the technical team makes changes elsewhere.

Maintaining operational control

DNS records are configuration assets.

They should have an owner, a documented purpose and a known destination.

A company that manages several domains should know which provider hosts each DNS zone, which services depend on the records and who is authorised to change them.

Monitoring and periodic audits help maintain that control.

3. How DNS checking tools work

A DNS checker starts with a question about a domain or hostname.

It then sends a DNS query or performs a series of tests and displays the response.

The important detail is where the query is sent.

A lookup through a recursive resolver, a query directly to an authoritative server and a distributed propagation test can produce different perspectives of the same domain.

Recursive DNS queries

A recursive resolver receives a query from a client and attempts to obtain the requested answer.

If it already has a valid cached response, it may return that response without contacting the authoritative server again.

If it does not have a suitable cached answer, it follows the DNS resolution process to obtain the information.

A browser-based DNS tool may use a particular public resolver.

The result therefore shows what that resolver returned at the time of the query.

Authoritative DNS queries

An authoritative server provides the official DNS data for a zone.

When an administrator needs to know what the domain currently publishes, querying the authoritative servers is especially important.

Suppose the DNS provider's control panel shows a new A record, but users still reach the old server.

A query to the authoritative name server helps determine whether the new value has actually been published.

If the authoritative server returns the new address while a recursive resolver returns the old one, caching may explain the difference.

Distributed propagation checks

Propagation services query resolvers from several locations and display the answers they receive.

This makes it easier to see whether selected resolvers are returning consistent information.

However, these services do not test every DNS resolver on the internet.

Their results represent a sample of the resolvers and locations included in the service.

A green result across the displayed locations is useful evidence, but it is not a guarantee that every ISP, corporate network or local cache has updated.

DNS health analysis

Health checkers perform several tests and combine the results into a report.

Depending on the service, the report may examine:

  • Nameserver delegation.
  • SOA records.
  • Glue records.
  • Authoritative server availability.
  • Response consistency.
  • Mail-server configuration.
  • DNSSEC deployment.
  • Common configuration warnings.

The value of a health report is that it provides a broader view than a single lookup.

The limitation is that not every warning represents a real fault.

Some findings depend on the provider's architecture or the way a zone is intentionally configured.

DNSSEC analysis

DNSSEC analysis follows the cryptographic chain of trust.

The checker examines information such as DS records, DNSKEY records and signatures to identify problems that may prevent validation.

A DNSSEC failure can occur even when the ordinary DNS records appear correct.

For example, a domain may publish the correct A record but have a DS record at the parent zone that no longer matches the DNSKEY information in the child zone.

Tools such as DNSViz and Verisign DNSSEC Debugger are designed for this type of investigation.

DNS performance testing

Performance tools measure how quickly DNS services answer queries.

They may compare resolvers from one local network or collect measurements from multiple global locations.

The test methodology matters.

A local benchmark helps evaluate resolver performance from the network where it is run.

A global service such as DNSPerf provides a wider comparison across its measurement locations.

DNSPerf describes tests from more than 200 locations and separates performance, uptime and quality views.

DNS monitoring

Monitoring services repeat checks at scheduled intervals.

Depending on the product, they may alert administrators when records change, when name servers become unavailable or when a website stops responding.

Monitoring is different from a one-time lookup.

A one-time lookup tells you what happened at a particular moment.

Monitoring creates an ongoing record that can help identify when a change or failure occurred.

4. DNS records every administrator should understand

A DNS checker is only useful if the person reading the result understands the record being tested.

These are the records most likely to appear in routine website, email and network administration.

RecordWhat it doesCommon reason to check it
AMaps a hostname to an IPv4 addressWebsite points to the correct server
AAAAMaps a hostname to an IPv6 addressIPv6 connectivity
CNAMEMakes one hostname an alias of anotherSubdomains and hosted services
MXIdentifies mail servers for a domainEmail routing
TXTPublishes text informationSPF, verification and policies
NSIdentifies authoritative name serversDomain delegation
SOAContains administrative information about a DNS zoneZone serial and authority
PTRMaps an IP address to a hostnameReverse DNS
SRVIdentifies the location of a serviceService discovery
CAASpecifies permitted certificate authoritiesCertificate issuance control
DSLinks a child zone to DNSSEC information in the parentDNSSEC delegation
DNSKEYPublishes DNSSEC public keysSignature validation


A and AAAA records

A records provide IPv4 addresses.

AAAA records provide IPv6 addresses.

A domain can use both.

When a website migration takes place, the administrator should check both records if the service supports IPv6.

An incorrect AAAA record can cause inconsistent access because some clients and networks may prefer IPv6.

CNAME records

A CNAME record points one hostname to another hostname.

It is commonly used for subdomains connected to SaaS platforms, website builders and external services.

CNAME records have DNS restrictions, including restrictions on using other ordinary record types at the same owner name.

Some providers offer special handling at the zone apex, but this should not be confused with a standard CNAME.

MX records

MX records specify the mail servers responsible for receiving email for a domain.

They include priority values that determine which servers are preferred.

During an email migration, administrators should confirm that the MX records match the new provider's instructions.

They should also consider caching and the transition period before retiring the previous mail service.

TXT records

TXT records support several functions, including domain verification and email authentication.

SPF policies are published as TXT records.

DKIM public keys are also commonly published through TXT records, while DMARC uses a TXT record at its dedicated policy hostname.

An organisation should maintain a record of why each important TXT value exists.

This prevents a future administrator from deleting a record that appears unfamiliar but is required by a business application.

NS and SOA records

NS records identify the authoritative name servers for a zone.

SOA records contain administrative information, including a serial number used in zone update processes.

During a migration, the registrar's delegation and the DNS provider's active zone must agree.

A perfectly configured zone at the wrong provider will not solve the problem.

PTR records

PTR records support reverse DNS.

They map an IP address back to a hostname and are relevant to several network services, including email infrastructure.

The organisation that controls the forward DNS zone may not control the reverse DNS zone.

The IP address provider or hosting company may need to configure the PTR record.

CAA, DS and DNSKEY records

CAA records control which certificate authorities are permitted to issue certificates for a domain.

DS and DNSKEY records are part of DNSSEC.

These records are particularly relevant during certificate deployment, DNSSEC configuration and DNS provider migrations.

Advertisement

5. Important features to look for in a DNS checker

Not every DNS checker offers the same capabilities.

Before choosing one, consider the following features.

Record-type coverage

A basic tool may support A, AAAA, MX, TXT, NS and CNAME.

More advanced tools may also support SOA, PTR, SRV, CAA, DS, DNSKEY and other record types.

For general website administration, common record coverage may be enough.

For enterprise DNS operations, a wider range is preferable.

Multiple resolver locations

A propagation checker should provide a useful selection of locations and resolvers.

The number of locations alone does not guarantee quality.

What matters is whether the service clearly identifies the perspective represented by each result.

Authoritative-server testing

The ability to query authoritative servers is valuable because it helps distinguish an incorrect published record from an older cached response.

Without this distinction, administrators may make unnecessary edits when the actual issue is resolver caching.

DNSSEC support

If an organisation uses DNSSEC, a basic record lookup is not enough.

Look for a tool that can examine the chain of trust and explain validation errors.

Email diagnostics

For organisations that depend on business email, support for MX, SPF, DKIM and DMARC checks is particularly useful.

A dedicated email diagnostic platform may provide more value than a general DNS checker.

Monitoring and alerts

A one-time check is useful during troubleshooting.

A monitoring service is more appropriate when the organisation needs to detect unexpected changes or service failures.

Look for suitable check intervals, notification channels, historical records and coverage for the DNS record types that matter to the business.

Performance measurements

If resolver performance is the objective, look for tools that explain their test methodology.

Results should be compared by location and over a meaningful period, not treated as a universal ranking.

Export and reporting

For professional IT operations, the ability to export results or share a report can be useful.

It helps document migrations, support requests, audits and incident investigations.

Ease of use and technical depth

A simple interface is valuable for occasional users.

Experienced administrators may prefer a tool that exposes detailed query information, authoritative responses and diagnostic context.

The right balance depends on the team that will use the tool.

6. Comparison of the 20 Best DNS Check Tools

The table below provides a practical overview of the 20 tools selected for this guide.

It distinguishes general lookup services from specialist platforms.

That distinction matters: a DNSSEC analyser should not be judged by the same criteria as a propagation checker, and a performance benchmark is not a substitute for a DNS health audit.

ToolMain purposeKey capabilitiesBest suited toGeneral cost position
Google Admin Toolbox DigDNS lookupDetailed record queries, DNS response inspectionAdministrators and developersFree
DNSCheckerDNS propagationMulti-location record checksWebsite owners and IT teamsFree checks; additional services may vary
WhatsMyDNSDNS propagationGlobal resolver comparisonBeginners and administratorsFree
MXToolboxDNS and email diagnosticsMX, SPF, DKIM, DMARC, blacklist and DNS checksEmail administratorsFree tools; paid advanced services
IntoDNSDNS healthDelegation, SOA, nameserver and zone checksSystem administratorsFree
DNSVizDNSSEC analysisDNSSEC chain visualisation and error analysisDNS specialistsFree
ZonemasterDNS zone testingDelegation, consistency, DNSSEC and pre-delegation testsDNS administratorsFree
Verisign DNSSEC DebuggerDNSSEC validationDS, DNSKEY and trust-chain diagnosisDNSSEC administratorsFree
dns.googlePublic resolver lookupQueries through Google Public DNSDevelopers and network teamsFree
Cloudflare DNS toolsDNS management and diagnosticsDNS record management, DNS learning resources and related testsCloudflare customers and administratorsFree tools; DNS service plans vary
ViewDNS.infoDomain and network lookupDNS lookups, propagation and other domain utilitiesWebsite owners and researchersFree utilities; service options vary
DNSlyticsDomain researchDNS and IP relationship researchSecurity and infrastructure teamsFree and paid features may vary
DNSdumpsterDNS reconnaissancePublic DNS information and subdomain discoverySecurity professionalsFree access subject to service limits
DNS SpyDNS monitoringRecord-change monitoring and alertsDomain administratorsService plan dependent
GRC DNS BenchmarkResolver benchmarkingLocal DNS speed, reliability and behaviour comparisonNetwork administratorsFree
DNSPerfDNS performance analyticsGlobal resolver and authoritative DNS comparisonsNetwork and infrastructure teamsFree public data
DNSLeakTestDNS privacy testingResolver identification and leak checksVPN users and privacy-conscious usersFree
Internet.nlInternet standards testingDNSSEC, IPv6, HTTPS and email standards checksIT and security teamsFree
NSLookup.ioDNS lookupBrowser-based record queries and DNS utilitiesDevelopers and general usersFree tools; current service limits apply
UptimeRobotAvailability monitoringWebsite and service uptime monitoringWebsite owners and IT operationsFree and paid plans


Cost descriptions are deliberately broad.

Web Hosting

Hostinger VPS

4.3
4.3

Hostinger VPS delivers KVM virtualization, NVMe storage and full root access at prices that undercut most competing cloud providers.

  • Strong price to specification ratio overall
  • NVMe storage included on every tier
  • Renewal rates climb steeply after promo
  • Self managed means security is your job
Read review Get Started Affiliate Link

Free access, monitoring limits and premium features can change.

Check each provider's current service and pricing pages before selecting a product for business use.

How to read the comparison

The tools fall into six practical groups:

  1. General DNS lookup: Google Admin Toolbox Dig, dns.google and NSLookup.io are useful when you need to inspect a specific DNS response.
  2. Propagation checking: DNSChecker and WhatsMyDNS help compare answers from selected locations.
  3. DNS health and email diagnostics: MXToolbox and IntoDNS cover broader configuration checks, with MXToolbox particularly relevant to mail.
  4. DNSSEC and zone validation: DNSViz, Zonemaster and Verisign DNSSEC Debugger provide specialist analysis.
  5. Research and security: ViewDNS.info, DNSlytics and DNSdumpster help investigate publicly visible domain and network information.
  6. Performance and monitoring: GRC DNS Benchmark, DNSPerf, DNS Spy and UptimeRobot address performance, record changes or service availability. Internet.nl adds a broader standards assessment, while DNSLeakTest focuses on resolver privacy.

A tool's position in this table is not a universal ranking.

The right choice depends on the job.

A company investigating a failed email migration should start with mail diagnostics, not a resolver speed benchmark.

7. Detailed reviews of the 20 tools

The following reviews examine each tool individually.

Each assessment covers its purpose, practical capabilities, strengths, limitations and the type of user who is most likely to benefit from it.

7.1 General DNS lookup and record inspection

1. Google Admin Toolbox Dig

Google Admin Toolbox Dig is one of the most practical browser-based tools for inspecting DNS records.

It provides a web interface for DNS queries and presents the response in a format familiar to administrators who already use the Dig command-line utility.

Its main strength is directness.

You enter a domain, select the type of information you want to inspect and review the response.

It is particularly useful when you need to check an A, AAAA, MX, TXT, NS or CNAME record without installing software or opening a terminal.

The tool is part of Google Admin Toolbox, a collection of utilities designed to help troubleshoot Google Workspace and internet-related issues.

The same toolbox includes Check MX, which focuses on common mail-related DNS configuration problems.

Key features

  • Browser-based DNS lookup.
  • Inspection of common DNS record types.
  • Detailed DNS response information.
  • Useful for reviewing email and website records.
  • Part of a wider collection of Google troubleshooting utilities.

Pros and cons

ProsCons
Free and easy to accessNot a complete DNS health monitoring platform
Familiar to administrators who use DigRequires some DNS knowledge to interpret detailed responses
Useful for checking several record typesDoes not provide a full global propagation map
No local installation requiredNot designed for ongoing record-change alerts
Part of Google's broader diagnostic toolboxA successful query does not prove the destination service is online


Advantages

The most important advantage is that it exposes useful DNS response information without requiring a command-line environment.

This makes it suitable for technical support, migration checks and everyday administration.

It is also a sensible first step when a user reports that a website or email service is not working.

The administrator can inspect the relevant records and compare the response with the configuration supplied by the hosting or email provider.

Disadvantages

The tool is not intended to replace a full DNS audit.

It does not continuously monitor a domain, and it does not provide the same global comparison as a dedicated propagation checker.

Users unfamiliar with DNS response details may also need additional explanation before they can interpret the output correctly.

Verdict

Best general-purpose lookup

Google Admin Toolbox Dig is an excellent starting point for administrators who need a reliable, accessible way to inspect DNS records.

It should be part of a technical team's basic toolkit, although more specialised tools are necessary for propagation, DNSSEC and monitoring.

2. DNSChecker

DNSChecker is designed to make DNS propagation checks easier to understand.

Instead of showing only one resolver's answer, it presents results from selected locations so that users can compare how DNS information is being returned across its network.

This is especially useful after changing a domain's A, AAAA, CNAME, MX, NS or TXT record.

A website owner can check whether the new destination is visible to the selected resolvers.

An email administrator can use the same approach to review an MX change.

The visual layout is one of its main attractions.

Users can identify locations returning the expected value and locations that still show a different answer.

This makes it easier to communicate a DNS issue to a hosting provider or another administrator.

Key features

  • Multi-location DNS checks.
  • Support for common DNS record types.
  • Visual comparison of returned values.
  • Useful after nameserver and hosting changes.
  • Accessible interface for non-specialist users.

Pros and cons

ProsCons
Simple interfaceDoes not test every resolver on the internet
Useful visual presentation of resultsDoes not replace authoritative-server diagnostics
Supports common record checksA location result may represent a limited resolver sample
Helpful after DNS migrationsDoes not establish whether the destination server is working
Suitable for quick support checksGlobal differences may require deeper investigation


Advantages

DNSChecker is particularly effective when the problem involves inconsistent results after a DNS change.

The visual comparison helps users see that a domain may return different answers through different resolvers.

It is also accessible to people who do not work with DNS every day.

A website owner can perform a check and share the result without understanding every detail of DNS resolution.

Disadvantages

The main limitation is the meaning of propagation.

A checker can only report what its selected resolvers return.

It cannot guarantee that every ISP, company network or local DNS cache has updated.

It also does not explain every cause of a mismatch.

If the authoritative name servers themselves publish inconsistent information, the administrator must investigate the zone and its delegation.

Verdict

Best for visual propagation checks

DNSChecker is a strong choice for website owners, developers and IT teams that regularly change DNS records.

Use it to compare resolver responses, then confirm the authoritative configuration before making additional changes.

3. WhatsMyDNS

WhatsMyDNS is a straightforward DNS propagation checker.

It allows users to enter a domain, choose a record type and compare the responses displayed from different locations.

Its simplicity is the main reason to use it.

The service is well suited to a quick check after changing a website address, moving a domain to a new DNS provider or updating email records.

For example, after changing a domain's nameservers at a registrar, an administrator can inspect the NS record responses.

If a website's A record has changed, the same service can help show whether selected resolvers return the new IP address.

WhatsMyDNS is particularly useful when users report different experiences from different networks.

It provides a quick way to establish whether the observed DNS answers are consistent across the service's test locations.

Key features

  • Multi-location DNS checks.
  • Common record-type lookups.
  • Visual results for quick comparison.
  • Useful for website and email migrations.
  • Simple browser-based operation.

Pros and cons

ProsCons
Very easy to useLimited depth for advanced DNS diagnosis
Useful for quick propagation snapshotsDoes not provide a complete zone audit
No installation requiredDoes not cover every resolver or ISP
Suitable for common record typesResults need interpretation alongside TTL and authoritative data
Useful for communicating basic findingsNot an ongoing monitoring system


Advantages

WhatsMyDNS works well when speed and simplicity matter.

An administrator can check a record without configuring a local DNS utility or navigating a complex interface.

It is also useful as a second opinion.

If DNSChecker reports an unexpected result, a separate propagation service can help determine whether the difference is consistent or specific to one testing network.

Disadvantages

It is not a diagnostic platform for complex delegation, DNSSEC or zone replication problems.

It can show that responses differ, but the administrator still needs to identify why.

The service also should not be treated as proof that a change has reached every user.

The displayed results are a sample, not a complete representation of global DNS caching.

Verdict

WhatsMyDNS is a good choice for straightforward propagation checks.

It is particularly suitable for website owners and smaller IT teams that need a simple visual result, but it should be paired with a detailed lookup tool for more complex incidents.

4. MXToolbox

MXToolbox is one of the most useful platforms for administrators responsible for business email and domain diagnostics.

Its collection of utilities covers DNS lookups, MX records, SPF, DKIM, DMARC, blacklist checks and other email-related investigations.

This breadth is important because email delivery rarely depends on one record alone.

An organisation may have a correct MX record but still experience authentication failures because its SPF policy is incomplete, DKIM is not configured properly or DMARC alignment is failing.

MXToolbox provides a convenient place to inspect several of these areas.

It is particularly useful during migrations from cPanel email or another hosted mail service to Microsoft 365, Google Workspace or a different provider.

Key features

  • MX record lookup.
  • SPF and email authentication checks.
  • DKIM and DMARC inspection.
  • DNS and domain diagnostics.
  • Blacklist-related checks.
  • Additional monitoring and reporting options, depending on the service plan.

Pros and cons

ProsCons
Broad email diagnostic coverageInterface can feel busy to new users
Useful for MX, SPF, DKIM and DMARCSome advanced features require a paid plan
Helps investigate mail delivery problemsDoes not prove that a mailbox or mail server is fully operational
Suitable for email migrationsFindings may require specialist knowledge
Combines several related checksA successful DNS check does not guarantee inbox placement


Advantages

MXToolbox is particularly valuable because it recognises that email troubleshooting requires several types of evidence.

Administrators can inspect mail routing and authentication records without using separate services for every basic check.

It is also useful for support work.

When a customer reports that messages are rejected or marked as suspicious, an administrator can collect information about the domain's published records and investigate the authentication configuration.

Disadvantages

The platform covers many areas, which can make the interface less approachable for someone who only needs a simple DNS lookup.

Advanced monitoring and reporting capabilities may also depend on paid service options.

It is important not to confuse a passing DNS test with successful email delivery.

Mail routing, server reputation, mailbox configuration, filtering and message content can all affect delivery.

Advertisement

Verdict

Best for email DNS diagnostics

MXToolbox is one of the strongest choices for email administrators.

If your work involves Microsoft 365, Google Workspace, hosted email or mail-server troubleshooting, it deserves a place in your regular toolkit.

5. IntoDNS

IntoDNS focuses on domain DNS health rather than a single record lookup.

It examines several aspects of a domain's configuration and presents warnings or findings that can help administrators identify problems with delegation, nameservers, SOA information and related DNS settings.

This is particularly useful during DNS migrations.

A domain can have the correct website A record but still have a wider configuration problem involving nameserver delegation or inconsistent authoritative servers.

IntoDNS provides a broader view that can help administrators decide where to investigate next.

Key features

  • DNS zone health report.
  • Nameserver and delegation checks.
  • SOA-related information.
  • Glue and configuration checks.
  • Identification of common DNS warnings.

Pros and cons

ProsCons
Provides a broader DNS report than a simple lookupNot every warning indicates a real operational fault
Useful during DNS migrationsInterface and report language may be technical
Helps identify delegation issuesDoes not provide continuous monitoring
No complex setup for a basic reportDoes not replace specialist DNSSEC analysis
Useful for inherited or unfamiliar domainsFindings may need verification with authoritative queries


Advantages

IntoDNS is useful when an administrator wants an initial assessment of a domain's configuration.

It can expose issues that would not be obvious from checking only the A or MX record.

It is also valuable when taking responsibility for a domain that another administrator previously managed.

A health report can help identify areas that deserve a closer review.

Disadvantages

A warning should not automatically be treated as an instruction to change the configuration.

DNS providers may use different architectures, and some findings may be acceptable in a particular environment.

IntoDNS is also not designed to alert an administrator when a record changes later.

It provides a diagnostic snapshot rather than ongoing operational monitoring.

Verdict

IntoDNS is a useful free DNS health checker for system administrators.

It is particularly helpful before and after migrations, provided that its warnings are verified rather than treated as automatic faults.

6. DNSViz

DNSViz is a specialist DNS analysis tool designed to visualise the status of a DNS zone and help troubleshoot DNSSEC deployment.

It presents the authentication chain and resolution path, making complex DNSSEC relationships easier to inspect.

DNSSEC failures can be difficult to understand because the problem may not be in the ordinary A, AAAA or MX record.

A domain can publish the expected address but still fail validation because a signature, key or delegation relationship is incorrect.

DNSViz helps identify these issues and displays the relationships between the relevant DNS components.

A DNS visualization tool

Key features

  • DNS zone visualisation.
  • DNSSEC chain-of-trust analysis.
  • Identification of configuration errors.
  • Resolution-path analysis.
  • Useful technical detail for specialist investigations.

Pros and cons

ProsCons
Strong DNSSEC diagnostic capabilitiesMore complex than a basic lookup tool
Visual representation of the trust chainRequires DNS knowledge to interpret fully
Helps identify validation failuresNot intended for routine propagation checks
Useful after DNS provider migrationsNot a general DNS monitoring platform
Free access to the analysis toolComplex reports may take time to understand


Advantages

DNSViz is particularly valuable when a domain uses DNSSEC and begins failing validation.

It can help an administrator identify whether the issue relates to delegation, keys, signatures or another part of the trust chain.

The visual presentation is a major advantage.

Instead of reviewing disconnected records, the administrator can examine how the components relate to one another.

Disadvantages

This is not the tool to recommend to a beginner who only wants to check a website's IP address.

It is designed for more technical analysis, and interpreting its output requires a basic understanding of DNSSEC.

It also does not replace ongoing monitoring.

A successful analysis represents the state observed during the test and does not guarantee that the zone will remain healthy.

Verdict

Best for DNSSEC visual analysis

DNSViz is one of the strongest specialist tools in this list.

For administrators who manage signed DNS zones or investigate validation failures, its detailed visual analysis is particularly useful.

7. Zonemaster

Zonemaster is a DNS testing platform developed through collaboration between AFNIC and IIS.

It performs a structured set of tests to assess the technical configuration of a DNS zone, including delegation, nameserver behaviour, consistency and DNSSEC.

One of its most useful capabilities is pre-delegation testing.

Administrators can test a zone before changing the registrar's nameserver delegation, which makes it valuable during planned migrations.

For example, a company moving DNS hosting to a new provider can prepare the zone, test it and correct problems before making the new name servers authoritative for the public domain.

Key features

  • Comprehensive DNS zone testing.
  • Delegation and nameserver checks.
  • DNSSEC-related tests.
  • Pre-delegation testing.
  • Detailed test findings and reports.

Pros and cons

ProsCons
Suitable for structured DNS testingMore detailed than many casual users need
Useful before a DNS migrationResults require technical interpretation
Tests delegation and nameserver behaviourNot a continuous DNS monitoring service
Helps identify zone configuration issuesDoes not replace application uptime monitoring
Useful for documenting test resultsSome findings need provider-specific context


Advantages

Zonemaster is especially useful for planned changes.

Testing a zone before delegation reduces the risk of moving a domain to a provider whose configuration is incomplete.

It also offers more structured analysis than a simple record lookup.

This makes it suitable for administrators who need to check several aspects of a zone rather than one hostname.

Disadvantages

The level of detail may be unnecessary for a simple website record change.

Users who do not understand delegation, SOA records or DNSSEC may find the report difficult to interpret.

It is also a test tool rather than a complete monitoring platform.

A zone that passes today can still become unavailable later because of a provider outage or an unauthorised change.

Verdict

Best for pre-migration zone testing

Zonemaster is an excellent choice for DNS administrators who want to validate a zone before changing delegation.

It is particularly useful in professional environments where DNS changes should be tested and documented before implementation.

8. Verisign DNSSEC Debugger

Verisign DNSSEC Debugger is a specialist tool for investigating DNSSEC validation and the chain of trust.

It helps administrators examine the relationship between the parent zone's DS information and the child zone's DNSKEY records.

This is particularly important after changing DNS providers.

The new provider may sign the zone with different keys, while the registrar still publishes a DS record associated with the previous configuration.

A mismatch can cause validating resolvers to reject DNS responses even when ordinary records appear correct.

The debugger provides a focused way to investigate this type of problem.

dnssec-analyzer-verisignlabs.gslb.verisign.com

Key features

  • DNSSEC validation diagnostics.
  • DS and DNSKEY analysis.
  • Trust-anchor support.
  • Alternative authoritative nameserver input.
  • Focused investigation of signed zones.

Pros and cons

ProsCons
Specialist DNSSEC diagnostic toolNot useful for ordinary record checks
Helps investigate DS and DNSKEY mismatchesRequires knowledge of DNSSEC
Supports alternative trust-anchor inputDoes not provide general propagation monitoring
Useful after DNS provider changesNot a complete domain security audit
Focused interface for validation workResults may need coordination with the registrar


Advantages

The tool is valuable because it concentrates on a problem that ordinary DNS lookup services may not explain.

It helps administrators investigate the DNSSEC trust relationship rather than simply showing whether a record exists.

This can save time during a migration or key rollover, when a domain appears to have valid records but validating resolvers still reject it.

Disadvantages

Its scope is narrow.

It is not designed to test general DNS health, compare global propagation or monitor website availability.

It also cannot make a DNSSEC deployment safe by itself.

Administrators must understand which provider controls the zone, which registrar publishes the DS record and how the change should be coordinated.

Verdict

Verisign DNSSEC Debugger is a useful specialist option for DNSSEC administrators.

It is not a general-purpose checker, but it provides value when the problem involves validation and the chain of trust.

9. dns.google

dns.google provides a way to query DNS information through Google Public DNS.

It is useful when an administrator wants to see what Google's resolver returns for a particular hostname and record type.

This provides a useful comparison point during troubleshooting.

If the local office resolver returns an old address but dns.google returns the new one, the difference may point towards local caching or resolver-specific behaviour.

The service should be understood as a view through Google's public resolver, not as a complete global propagation test.

Key features

  • Browser-based DNS query interface.
  • Queries through Google Public DNS.
  • Support for DNS record lookups.
  • Useful for comparing resolver responses.
  • Accessible without installing a local utility.

Pros and cons

ProsCons
Free and easy to accessRepresents Google's resolver perspective
Useful independent comparison pointNot a multi-location propagation map
No local installation requiredDoes not provide a complete zone health report
Helpful for investigating resolver differencesDoes not replace authoritative-server checks
Useful for developers and administratorsNot an ongoing monitoring service


Advantages

dns.google is particularly helpful when a team needs to compare a local DNS result with a public resolver.

This can help narrow down whether the problem is associated with the local network, recursive resolver or authoritative configuration.

It is also straightforward to use and does not require a specialist interface.

Disadvantages

The result represents one resolver service.

It cannot tell an administrator what every ISP or corporate network is returning.

It also does not provide the detailed DNSSEC visualisation or zone health reporting available from specialist tools.

Verdict

dns.google is a useful secondary lookup tool.

It is particularly good for checking how a domain resolves through Google Public DNS, but it should be combined with authoritative queries and propagation checks when investigating inconsistent results.

10. Cloudflare DNS tools

Cloudflare provides DNS services, management features and technical resources that help administrators understand and operate DNS.

For domains hosted on Cloudflare, the dashboard is the main place to review and manage the zone's records.

It is important to distinguish this from an independent DNS checker.

The dashboard shows the configuration managed through the Cloudflare account.

An external lookup service shows what a selected resolver currently returns.

That distinction matters during a migration.

A record can appear correct in the Cloudflare dashboard while the registrar still delegates the domain to another DNS provider.

Cloudflare's DNS documentation also explains concepts such as DNS records, caching, DNSSEC and resolver behaviour.

toolbox.googleapps.com

+1

Key features

  • DNS record management for hosted zones.
  • Dashboard-based record review.
  • DNS-related documentation and learning resources.
  • DNSSEC configuration support.
  • Integration with Cloudflare's wider DNS and security services.

Pros and cons

ProsCons
Useful for domains hosted on CloudflareDashboard is not an independent global checker
Combines DNS management with related servicesSome features depend on Cloudflare configuration
Clear control over zone recordsNot a substitute for external propagation testing
Strong technical documentationDoes not diagnose every third-party resolver issue
Suitable for website and infrastructure administratorsUsers must understand proxy and DNS behaviour


Advantages

Cloudflare is particularly useful when the organisation already uses it as its authoritative DNS provider.

The administrator can review the zone and manage records from the same environment.

Its documentation is also helpful for understanding DNS behaviour and the relationship between DNS, caching, security and web delivery.

Disadvantages

It should not be treated as a neutral, independent diagnostic service.

A dashboard can show what is configured in the account, but it does not prove that the registrar delegation is correct or that all external resolvers have updated.

The distinction between DNS-only and proxied records can also confuse administrators who are new to Cloudflare.

Verdict

Cloudflare's DNS tools are most valuable for administrators who manage domains through Cloudflare.

Use the dashboard for zone management and an independent checker to verify what external resolvers actually return.

7.2 Domain research and DNS reconnaissance

11. ViewDNS.info

ViewDNS.info is a collection of domain and network utilities.

It offers several lookup tools that can help users investigate DNS information, IP addresses, domain details and related infrastructure.

It is useful when an administrator needs more context than a single DNS response.

For example, a website owner may want to check propagation, inspect an IP address or gather basic information about an unfamiliar domain.

Its range of utilities makes it a convenient secondary resource during an investigation.

Key features

  • DNS lookup utilities.
  • DNS propagation checks.
  • Reverse IP and related network lookups.
  • Domain information tools.
  • Multiple browser-based diagnostic utilities.

Pros and cons

ProsCons
Several utilities in one placeNot every utility is a full DNS diagnostic
Useful for domain researchResults may need verification elsewhere
Accessible through a browserNot a replacement for authoritative DNS tools
Can provide useful network contextDoes not offer the same depth as specialist DNSSEC tools
Useful as a secondary sourceService limits and features may vary


Advantages

ViewDNS.info is convenient when an investigation requires several related lookups.

Instead of opening a different website for every basic domain or IP question, the administrator can use a collection of utilities from one interface.

It can also help users who are researching an unfamiliar domain or checking information related to an IP address.

Disadvantages

The broad scope means that the platform should not be treated as a specialist solution for every task.

A reverse IP lookup, for example, does not establish that all domains associated with an address belong to the same organisation.

For critical DNS changes, authoritative queries and provider documentation remain essential.

Verdict

ViewDNS.info is a useful general research toolbox.

It is best used as a supporting resource rather than the primary diagnostic platform for complex DNS incidents.

12. DNSlytics

DNSlytics focuses on domain and infrastructure research.

It can help users investigate information associated with domains, IP addresses and DNS relationships.

This is particularly relevant to security teams and administrators who need to understand an organisation's external footprint.

Advertisement

Rather than asking only where one hostname resolves, they may want to examine related infrastructure and discover information that deserves further review.

DNSlytics can support these investigations by providing domain and network context.

Key features

  • Domain and DNS research.
  • IP-related information.
  • Infrastructure relationship research.
  • Domain discovery and investigation utilities.
  • Support for external footprint reviews.

Pros and cons

ProsCons
Useful for domain researchNot a complete DNS health checker
Helps investigate IP and domain relationshipsShared hosting can create misleading associations
Relevant to security and infrastructure reviewsData may not reflect every recent change
Provides context beyond a single lookupFindings need independent verification
Useful for technical researchSome capabilities may depend on service access level


Advantages

DNSlytics is useful when the administrator wants to understand more about a domain's surrounding infrastructure.

This can help during an external asset review, an investigation of suspicious domains or a security assessment.

It provides a broader research perspective than a basic A or MX lookup.

Disadvantages

Infrastructure relationships can be misleading if they are interpreted without context.

Several unrelated domains may share an IP address because they use the same hosting provider, reverse proxy or content delivery network.

A relationship discovered by a research tool is not proof of common ownership or malicious activity.

Verdict

DNSlytics is a useful supporting tool for security and infrastructure research.

It is not the first choice for routine record verification, but it can provide valuable context during a wider domain investigation.

13. DNSdumpster

DNSdumpster is a DNS reconnaissance tool that helps users discover publicly visible infrastructure associated with a domain.

It is particularly relevant to security assessments and external asset discovery.

A company may have several subdomains for its website, email, remote access, customer portal and business applications.

A reconnaissance tool can help identify hostnames that should be included in an asset inventory.

For authorised security teams, this information can be useful before a penetration test or external infrastructure review.

Key features

  • DNS reconnaissance.
  • Public hostname discovery.
  • Subdomain research.
  • Infrastructure mapping support.
  • Browser-based domain investigation.

Pros and cons

ProsCons
Useful for external reconnaissanceResults may be incomplete
Helps discover publicly visible hostnamesDoes not prove that a host is active
Relevant to authorised security assessmentsNot a general DNS record monitoring tool
Provides broader infrastructure contextDiscovered assets need verification
Useful for initial asset inventoriesNot a vulnerability scanner


Advantages

DNSdumpster helps security professionals look beyond the main website hostname.

It can reveal additional names that should be checked during an external security review.

This is useful because organisations sometimes forget older subdomains, test environments or third-party services that remain publicly visible.

Disadvantages

Discovery results are not a complete inventory.

Some hostnames may be missing, outdated or no longer active.

The presence of a hostname does not prove that the service is exposed or vulnerable.

The tool should also be used only within authorised research and assessment activities.

Verdict

Web Hosting

Hostinger VPS

4.3
4.3

Hostinger VPS delivers KVM virtualization, NVMe storage and full root access at prices that undercut most competing cloud providers.

  • Strong price to specification ratio overall
  • NVMe storage included on every tier
  • Renewal rates climb steeply after promo
  • Self managed means security is your job
Read review Get Started Affiliate Link

DNSdumpster is a useful reconnaissance resource for security professionals.

It is best suited to discovery and asset mapping, not routine DNS administration or ongoing availability monitoring.

7.3 DNS monitoring and performance

14. DNS Spy

DNS Spy is focused on DNS monitoring and change detection.

Its purpose is to help administrators keep track of DNS records rather than relying entirely on occasional manual lookups.

This is valuable for organisations that manage several domains or depend on DNS for business-critical services.

A record may be changed accidentally during a migration, altered by a third-party provider or modified by someone with access to the DNS account.

A monitoring service can help detect unexpected changes and give the technical team a reason to investigate.

Key features

  • DNS record monitoring.
  • Change detection.
  • Alerts for monitored DNS changes.
  • Historical visibility, depending on the service plan.
  • Support for domain administration workflows.

Pros and cons

ProsCons
Focuses on DNS change monitoringNot intended as a complete DNS diagnostic suite
Helps identify unexpected changesMonitoring scope and limits depend on the service
Useful for critical business domainsDoes not prevent unauthorised changes
Reduces dependence on manual checksAlerts require a response process
Supports operational visibilityDoes not replace website uptime monitoring


Advantages

DNS Spy addresses a different problem from a one-time lookup service.

It helps administrators notice when a record changes, which is particularly useful when the organisation needs to maintain a known DNS configuration.

For companies with multiple domains, monitoring can reduce the time between an unexpected change and the technical team's awareness of it.

Disadvantages

Monitoring does not prevent an attacker or administrator from changing a record.

It only helps detect changes after they occur.

The organisation still needs strong account security, access control and an incident-response process.

It is also important to review the current service limits, record coverage, alert options and historical retention before relying on it for production operations.

Verdict

Best for DNS change monitoring

DNS Spy is a good fit for administrators who need ongoing visibility into important DNS records.

It is particularly useful when unexpected changes could disrupt business services.

15. GRC DNS Benchmark

GRC DNS Benchmark is a utility for comparing DNS resolver performance and behaviour from the user's own network.

It can test multiple nameservers and report response times, reliability and other characteristics.

This is useful when an administrator wants to evaluate the DNS resolvers used by an office network or compare them with alternative public resolvers.

GRC explains that the benchmark can analyse up to 200 DNS nameservers and examine factors such as cached lookup performance, reliability and redirection behaviour.

It also supports detailed results and export options.

Key features

  • Local DNS resolver benchmarking.
  • Comparison of multiple nameservers.
  • Response-time analysis.
  • Reliability and behaviour checks.
  • Detailed reporting and export options.

Pros and cons

ProsCons
Detailed local resolver comparisonPrimarily designed for desktop use
Tests from the user's own networkResults may differ in other locations
Can compare many nameserversRequires interpretation of benchmark results
Provides detailed reportsNot a DNS zone health checker
Useful for network optimisationDoes not monitor domain record changes


Advantages

The most important advantage is that it measures performance from the network where the user runs the test.

This is useful because resolver performance depends partly on location, routing and network conditions.

It also provides more than a simple speed ranking.

Administrators can examine reliability and resolver behaviour, which are relevant when choosing a DNS service for a particular environment.

Disadvantages

A result from one office should not be treated as a universal ranking.

A resolver that performs well in one location may not perform equally well for users in another country.

The tool also does not check whether a domain's DNS zone is correctly configured.

It evaluates resolvers, not the complete health of a particular domain.

Verdict

Best for local resolver benchmarking

GRC DNS Benchmark is particularly useful for network administrators who want to compare DNS resolver performance from their own environment.

It is a specialist tool rather than a general DNS checker.

16. DNSPerf

DNSPerf provides DNS performance analytics and comparisons for authoritative DNS providers and public DNS resolvers.

It is useful when an organisation wants to compare DNS services using measurements collected across multiple locations.

Its public information separates performance, uptime and quality views.

DNSPerf describes tests conducted every minute from more than 200 locations, with public data updated periodically.

This makes it useful for infrastructure planning and resolver research.

Instead of relying only on a provider's marketing claims, administrators can examine comparative measurements and consider how the services perform across different locations.

Key features

  • DNS resolver performance comparisons.
  • Authoritative DNS provider comparisons.
  • Uptime and quality views.
  • Location-based performance information.
  • Historical performance views.

Pros and cons

ProsCons
Broad measurement footprintPublic results may not match a user's local network
Compares several DNS servicesBenchmark methodology must be understood
Includes uptime and quality informationNot a domain-specific DNS health checker
Useful for infrastructure researchDoes not monitor an organisation's own records
Public data is accessiblePerformance rankings can change over time


Advantages

DNSPerf is valuable when comparing DNS services at a broader level.

Its location and time-period options help users understand that resolver performance is not a fixed number.

It is also useful for infrastructure planning.

An organisation evaluating a DNS provider can use the public data as one source of evidence alongside service requirements, support, security and cost.

Disadvantages

Global benchmark data does not automatically predict the performance experienced by a specific office or customer.

Network routing, local connectivity, resolver caching and geography can all influence the result.

DNSPerf also does not diagnose an individual domain's incorrect A, MX or TXT record.

It measures DNS service performance rather than providing a complete zone audit.

Verdict

Best for global DNS performance comparison

DNSPerf is a strong resource for teams evaluating DNS resolver and authoritative DNS performance.

It is most useful for research and infrastructure decisions, rather than everyday record troubleshooting.

17. DNSLeakTest

DNSLeakTest helps users identify which DNS resolvers are handling their queries.

It is particularly relevant when someone uses a VPN and wants to check whether DNS requests are following the expected network path.

A VPN may encrypt traffic between a device and the VPN endpoint, but DNS configuration still matters.

If DNS requests are sent through the user's ordinary ISP resolver rather than the intended VPN resolver, information about the domains being queried may be exposed to that resolver.

DNSLeakTest provides a way to inspect the resolver information observed during its test.

Key features

  • DNS resolver identification.
  • DNS leak testing.
  • Useful during VPN configuration checks.
  • Browser-based testing.
  • Simple results for privacy investigations.

Pros and cons

ProsCons
Easy to useNot a complete VPN security audit
Useful for detecting unexpected resolver pathsDoes not test every aspect of network privacy
No installation required for basic testingResults can depend on browser and network conditions
Helpful for VPN troubleshootingNot intended for DNS zone management
Free access to basic testsDoes not provide DNS change monitoring


Advantages

The tool provides a practical check for users who want to know which DNS resolvers are visible while they use a VPN.

It can help identify a configuration that deserves further investigation.

It is also accessible to non-specialists, making it useful for basic privacy checks.

Disadvantages

A successful DNS leak test does not prove that a VPN is secure in every respect.

It does not establish that all traffic is routed correctly, that the VPN has no vulnerabilities or that the device is free from other privacy risks.

It is also not designed for website owners who need to inspect their domain's DNS records.

Verdict

DNSLeakTest is a useful specialist tool for VPN and privacy checks.

It should be used as one part of a broader review of network configuration, not as proof of complete VPN security.

18. Internet.nl

Internet.nl provides tests for modern internet standards.

Its website and email tests examine several aspects of internet configuration, including IPv6, DNSSEC, HTTPS, email authentication and secure transport.

This makes it broader than a conventional DNS checker.

It is useful for organisations that want to assess whether their internet-facing services support modern standards and security practices.

The service provides separate tests for websites, email and internet connections.

Its published test areas include DNSSEC, IPv6, HTTPS and email security-related standards.

internet.nl

Key features

  • Domain and website standards testing.
  • DNSSEC checks.
  • IPv6 assessment.
  • HTTPS testing.
  • Email security and transport checks.
  • Overall standards-oriented reporting.

Pros and cons

ProsCons
Covers several modern internet standardsNot a dedicated propagation checker
Useful DNSSEC and IPv6 checksScores need to be interpreted in context
Includes website and email testingSome findings may require specialist knowledge
Helpful for periodic technical reviewsDoes not replace a full security audit
Free public testingNot a continuous record-change monitoring service


Advantages

Internet.nl is useful because it places DNS within a broader internet standards review.

An organisation can use it to identify areas where its website or email configuration could be improved.

It is also suitable for periodic reviews, especially when a company wants to establish a baseline and measure progress.

Disadvantages

A score is not a complete security certification.

Administrators should examine the individual findings and decide which changes are appropriate for their environment.

It is also not intended to show whether a record has propagated to every resolver or whether a particular DNS provider is currently experiencing an outage.

Verdict

Best for modern internet standards testing

Internet.nl is a valuable tool for IT and security teams that want to assess DNSSEC, IPv6, HTTPS and email standards together.

It complements the more focused DNS lookup and propagation services.

19. NSLookup.io

Website: NSLookup.io

NSLookup.io provides browser-based DNS lookup tools for users who want to inspect records without installing software or using a terminal.

It is useful for checking common records during website deployment, email configuration and domain verification.

A developer may use it to confirm a CNAME record for an application, while an administrator may inspect MX or TXT records after an email migration.

The browser-based approach makes it accessible to both technical and non-technical users.

Key features

  • Browser-based DNS lookups.
  • Common DNS record inspection.
  • Domain troubleshooting utilities.
  • Useful for website and email configuration checks.
  • Accessible interface for quick queries.

Pros and cons

ProsCons
Easy to accessNot a complete DNS health audit
No local installation requiredLimited compared with specialist DNSSEC tools
Useful for common record checksNot a replacement for authoritative-server testing
Suitable for developers and website ownersDoes not provide full monitoring by itself
Convenient for quick verificationUsers may need another tool for propagation comparison


Advantages

NSLookup.io is useful when the administrator needs a quick browser-based lookup.

It reduces the barrier for people who do not use command-line DNS utilities regularly.

It is also practical during development and deployment, when records need to be checked several times as a custom domain is connected to an application or service.

Disadvantages

A simple lookup is not enough to diagnose complex DNS problems.

If a domain has inconsistent authoritative servers, a DNSSEC failure or different cached answers across locations, additional tools are needed.

It should also not be treated as a continuous monitoring platform unless the specific service features and plan support the monitoring requirements.

Verdict

NSLookup.io is a useful everyday lookup service for developers and general users.

It is best suited to quick record verification and should be paired with more specialised tools for complex troubleshooting.

Advertisement

20. UptimeRobot

Website: UptimeRobot

UptimeRobot is primarily an uptime monitoring platform rather than a dedicated DNS record checker.

It belongs in this guide because DNS problems often appear to users as website or service outages, and availability monitoring helps detect those incidents.

A website monitor can alert an administrator when a monitored endpoint stops responding.

The alert does not automatically prove that DNS is responsible, but it gives the technical team a signal to investigate.

For example, if a company website becomes unavailable, the administrator can combine an uptime alert with DNS lookups to determine whether the domain resolves correctly and whether the destination server responds.

UptimeRobot's own DNS monitoring comparison distinguishes record-related checks from broader uptime monitoring and explains that DNSSEC validation depth varies between monitoring platforms.

UptimeRobot Knowledge Hub

Key features

  • Website and service uptime monitoring.
  • Availability alerts.
  • Monitoring of public endpoints.
  • Incident visibility over time.
  • Integration with operational notification workflows, depending on the plan.

Pros and cons

ProsCons
Useful for detecting website outagesNot a full DNS zone analyser
Helps alert IT teams when services failAn alert does not identify DNS as the cause
Suitable for ongoing availability monitoringDNS-specific monitoring depends on available monitor types
Useful for incident responseAdvanced features may require a paid plan
Complements DNS diagnostic toolsDoes not replace record verification


Advantages

UptimeRobot provides operational visibility that a one-time DNS lookup cannot.

It helps teams discover when a public service becomes unavailable, rather than waiting for a customer or employee to report the problem.

It is also useful when combined with DNS tools.

The uptime alert identifies the symptom, while record lookups and server tests help establish the cause.

Disadvantages

An unavailable website may be caused by DNS, hosting, TLS, application errors, firewalls or network routing.

Uptime monitoring alone cannot distinguish all these causes.

It should therefore be used alongside record checks and application-level diagnostics, not as a replacement for them.

Verdict

Best as a DNS troubleshooting companion

UptimeRobot is a useful choice for organisations that need to monitor website and service availability.

It complements DNS checkers, although it should not be presented as a substitute for a dedicated DNS health or DNSSEC analysis platform.

8. How to choose the right DNS checker

Choosing a DNS checker should begin with the problem you want to solve.

Buying or adopting a large monitoring platform when all you need is a simple A-record lookup adds unnecessary complexity.

Equally, relying on a free propagation checker to investigate a DNSSEC failure is unlikely to produce a satisfactory answer.

The following considerations help narrow the choice.

Identify the type of DNS work

Start by identifying whether you need to look up records, compare propagation, audit a zone, investigate DNSSEC, measure resolver performance or monitor changes.

For a single record, Google Admin Toolbox Dig or NSLookup.io is sufficient in many cases.

For propagation, DNSChecker and WhatsMyDNS are more appropriate.

For a broader health report, IntoDNS or Zonemaster provides more context.

If the issue involves DNSSEC, use DNSViz or Verisign DNSSEC Debugger.

If it involves email, MXToolbox is a better starting point than a general-purpose lookup service.

Consider the user's technical experience

A tool should be understandable to the person who needs to use it.

A website owner may only need to confirm that a new IP address appears in the lookup result.

An experienced DNS administrator may want detailed response information, delegation tests and DNSSEC validation.

The right tool should expose enough information for the task without forcing users to interpret technical details they do not need.

For a mixed IT team, it can be useful to maintain a small collection of tools with different levels of complexity.

A support technician can use a simple lookup, while a senior administrator can investigate a complex zone problem with specialist software.

Check which record types are supported

A tool that only checks A and MX records may be adequate for basic website and email tasks, but it is not enough for every business environment.

Consider whether you need to inspect:

  • A and AAAA for website addresses.
  • CNAME for hosted services and subdomains.
  • MX for mail routing.
  • TXT for SPF, DKIM, DMARC and verification.
  • NS and SOA for delegation and zone administration.
  • PTR for reverse DNS.
  • SRV for service discovery.
  • CAA for certificate issuance restrictions.
  • DS and DNSKEY for DNSSEC.

If the organisation manages several services through one domain, wider record support is preferable.

Evaluate the quality of the results

A DNS checker should explain what it tested and what its result represents.

For propagation checks, look for clear location and resolver information.

For health checks, examine the individual warnings rather than relying only on a summary score.

For performance tests, review the methodology and measurement locations.

A result without context can create false confidence.

An administrator should know whether the tool queried an authoritative server, a recursive resolver or a local DNS service.

Decide whether monitoring is necessary

A one-time lookup is suitable for a manual check.

It is not enough when a business needs to know if a critical DNS record changes unexpectedly.

For a public website, uptime monitoring may be sufficient to detect service interruptions.

For a domain where unexpected record changes could have serious consequences, dedicated DNS monitoring is more appropriate.

Consider:

  • How often the tool checks records.
  • Which record types it supports.
  • Whether it compares results with expected values.
  • Whether it records old and new values.
  • How long it retains history.
  • Which notification channels it supports.
  • Whether it can monitor several domains.
  • Whether the monitoring service itself provides sufficient reliability.

Consider privacy and security

DNS lookup services receive the names users submit for testing.

For public domains this is usually not a major concern, but internal hostnames, unpublished project names and sensitive infrastructure details should not be submitted casually to third-party websites.

Before using an external service for internal DNS, review its privacy and data-handling policies.

For confidential environments, use approved internal tools or run tests from infrastructure controlled by the organisation.

Review cost against operational value

A free DNS checker can be sufficient for a small website.

A business with many domains, multiple teams and strict availability requirements may need paid monitoring, reporting or integration features.

The question is not simply whether a tool is free.

It is whether it provides the coverage the organisation needs.

For example, a free lookup service may be perfectly adequate for checking a TXT record once a month.

It is not a substitute for a monitoring platform that alerts the team when a critical MX or NS record changes.

Use more than one tool when necessary

Different tools provide different perspectives.

A strong troubleshooting process often combines two or three tools rather than relying on one platform.

For example:

  • Google Admin Toolbox Dig to inspect the record.
  • DNSChecker to compare selected resolver responses.
  • Zonemaster to assess the zone and delegation.
  • DNSViz to investigate DNSSEC.
  • MXToolbox to review email configuration.

This approach avoids trying to force one tool to answer every question.

9. Practical DNS troubleshooting scenarios

The following scenarios show how the tools can be used in real IT operations.

They also demonstrate why the order of investigation matters.

Scenario 1: A website still points to the old hosting provider

An organisation has moved its website to a new server.

The application is working, the database has been migrated and the new server responds correctly when accessed directly.

However, some visitors still see the old website.

The first step is to inspect the A record.

Google Admin Toolbox Dig or NSLookup.io can show the address returned by the DNS query.

Next, use DNSChecker or WhatsMyDNS to compare selected resolver responses.

If some locations return the new address and others return the old one, caching may be involved.

The administrator should then query the authoritative name servers.

If they publish the new address, the DNS zone may be correct and some recursive resolvers may still have the previous value cached.

If the authoritative servers still publish the old address, check whether the correct DNS provider was edited.

The registrar may still delegate the domain to the previous provider.

Recommended tools: Google Admin Toolbox Dig, DNSChecker, WhatsMyDNS and IntoDNS.

What not to do: Do not keep changing the A record because one user still sees the old website.

Confirm the authoritative answer and the relevant TTL first.

Scenario 2: Email stops arriving after a migration

A company moves its email service from a cPanel server to Microsoft 365.

Users can send some messages, but external senders report that messages are delayed or delivered to the old mail server.

Start by checking the MX record with MXToolbox or Google Admin Toolbox Dig.

Compare the result with the Microsoft 365 configuration instructions for the organisation's domain.

If the MX record is correct, inspect the other email-related records.

SPF, DKIM and DMARC should also be reviewed, although they serve authentication purposes rather than incoming mail routing.

If the authoritative MX record is correct but some senders still use the previous destination, caching may explain the difference.

The migration plan should account for the old service remaining available during the transition where necessary.

Recommended tools: MXToolbox, Google Admin Toolbox Dig and DNSChecker.

What not to do: Do not assume that a successful MX lookup proves the entire email migration is complete.

Test actual message delivery, authentication and mailbox access.

Scenario 3: A domain fails after DNSSEC is enabled

A website works for some users but fails for others.

The problem began after the organisation enabled DNSSEC or changed DNS providers.

This is a case for DNSViz or Verisign DNSSEC Debugger.

The administrator should inspect the chain of trust and compare the DS information at the parent zone with the DNSKEY records published by the child zone.

If the DNS provider changed its signing keys but the registrar still publishes an old DS record, validating resolvers may reject the DNS responses.

The correction must be coordinated between the registrar and DNS provider.

The administrator should not remove or alter DNSSEC records without understanding the impact.

Recommended tools: DNSViz and Verisign DNSSEC Debugger.

What not to do: Do not disable DNSSEC as a first reaction.

Identify the exact validation failure and correct the relevant part of the chain.

Scenario 4: One office cannot access a website

Employees in one office report that a website is unavailable, but users on mobile networks and other company locations can access it.

The administrator should compare DNS responses from the affected office and an external network.

If the office uses an internal DNS server, inspect the resolver configuration and any internal DNS zones.

The office may have a stale cache, a forwarding issue or a local record that overrides public DNS.

A lookup through dns.google can provide a comparison with Google Public DNS.

DNSChecker can help show whether selected external resolvers return the expected value.

If all DNS responses are correct, investigate routing, firewall policies, proxy settings and the destination server.

Recommended tools: Google Admin Toolbox Dig, dns.google, DNSChecker and the organisation's internal DNS tools.

What not to do: Do not assume that a public DNS change is the cause just because one office cannot access the service.

The fault may be local to that network.

Scenario 5: A new subdomain does not connect to a SaaS application

A developer creates a subdomain for a hosted application.

The provider asks for a CNAME record and a TXT verification record.

The subdomain remains unavailable after the change.

Start by checking both records.

Confirm that the CNAME points to the exact hostname supplied by the service provider and that the TXT verification value has been published at the correct name.

Use Google Admin Toolbox Dig or NSLookup.io for the individual lookups.

If results differ across resolvers, use DNSChecker to compare responses.

Also review the provider's instructions.

Some services require the user to complete domain verification in the application dashboard after publishing the DNS record.

Recommended tools: Google Admin Toolbox Dig, NSLookup.io and DNSChecker.

What not to do: Do not replace the CNAME with an IP address unless the provider explicitly instructs you to do so.

The provider may manage the destination infrastructure dynamically.

Scenario 6: The company wants to identify all public subdomains

An organisation is preparing an external security assessment and wants to review the hostnames associated with its domain.

Advertisement

DNSdumpster and DNSlytics can help with public DNS reconnaissance.

The security team can use the findings to build an initial list of hostnames and compare it with the organisation's internal asset inventory.

The next step is to verify which discovered hosts are active and who owns them.

Some records may be outdated, and some hostnames may belong to third-party services.

Recommended tools: DNSdumpster, DNSlytics and ViewDNS.info.

What not to do: Do not assume that every discovered hostname is an active company-owned server.

Verify ownership and service status before including it in the final asset register.

Scenario 7: The IT team wants to improve DNS resolution speed

A company receives complaints that websites take too long to begin loading.

The network administrator suspects that DNS resolution may be contributing to the delay.

GRC DNS Benchmark can compare resolver performance from the office network.

DNSPerf can provide wider performance information across its measurement locations.

The administrator should test more than one time period and consider the location of the resolvers.

If the company has offices in different countries, each location may need its own assessment.

The final choice should consider security, reliability, privacy and policy requirements, not speed alone.

Recommended tools: GRC DNS Benchmark and DNSPerf.

What not to do: Do not change the organisation's DNS resolver based on one test from one computer.

Confirm that the new resolver is suitable for the wider network.

Scenario 8: The organisation wants to detect unexpected DNS changes

A company depends on its website, email and customer portal.

The IT team wants to know if important records change outside the approved maintenance process.

A DNS monitoring service such as DNS Spy can help track record changes.

The organisation should define which records matter, who receives alerts and how the team will investigate unexpected modifications.

UptimeRobot can provide a separate signal if a public service becomes unavailable.

The monitoring process should be supported by registrar account protection, multi-factor authentication, access restrictions and a documented change-control procedure.

Recommended tools: DNS Spy and UptimeRobot.

What not to do: Do not treat monitoring as a substitute for access control.

An alert tells the team that a change occurred; it does not prevent the change.

Scenario 9: The organisation wants to review internet standards

A technical team wants to assess whether its website and email configuration follow modern internet standards.

Internet.nl can provide a broader review of DNSSEC, IPv6, HTTPS and email-related standards.

The results can help identify areas for improvement.

The administrator should review individual findings and decide which changes are appropriate for the organisation's architecture.

A standards test is useful evidence, but it is not a complete security audit.

Recommended tool: Internet.nl.

What not to do: Do not focus only on the overall score.

Understand each failed test and its operational significance.

Scenario 10: A VPN user suspects DNS leakage

An employee connects to a VPN but wants to confirm that DNS requests are handled through the expected resolver.

DNSLeakTest can show the resolver information observed during the test.

Web Hosting

Hostinger VPS

4.3
4.3

Hostinger VPS delivers KVM virtualization, NVMe storage and full root access at prices that undercut most competing cloud providers.

  • Strong price to specification ratio overall
  • NVMe storage included on every tier
  • Renewal rates climb steeply after promo
  • Self managed means security is your job
Read review Get Started Affiliate Link

If the results indicate an unexpected resolver, the user or IT team should review VPN DNS settings, operating system configuration and any split-tunnelling policy.

The organisation should also test the behaviour after reconnecting and from different network environments.

Recommended tool: DNSLeakTest.

What not to do: Do not treat a single successful test as proof that the VPN protects every aspect of the user's network traffic.

10. A professional DNS troubleshooting workflow

A repeatable workflow is more valuable than a long list of tools.

It ensures that administrators collect evidence before changing production records.

Step 1: Define the affected service

Identify the exact hostname and service.

Do not simply record that "the domain is down".

The problem may affect the root domain, the www hostname, a mail server, a customer portal or an application subdomain.

Each may use different records.

Record when the issue started, who is affected and whether the problem occurs on every network.

Step 2: Establish the expected configuration

Obtain the expected DNS values from the hosting provider, email provider or application owner.

Do not rely on memory or an old screenshot.

A migration may have introduced a new IP address or provider hostname.

Record the relevant hostname, record type, expected value and purpose.

Step 3: Query the current records

Use Google Admin Toolbox Dig or NSLookup.io to inspect the published records.

Check the record type that corresponds to the service.

For a website, inspect A and AAAA.

For email routing, inspect MX.

For a hosted application, inspect the required CNAME and verification TXT records.

Step 4: Check the authoritative name servers

Inspect the NS records and identify the authoritative servers.

Confirm that the registrar delegates the domain to the provider whose DNS zone you are editing.

This step prevents one of the most common administrative mistakes: changing records in a control panel that is not currently authoritative for the domain.

Step 5: Compare responses through other resolvers

Use DNSChecker, WhatsMyDNS or dns.google to compare resolver answers.

If the results differ, record which resolvers return which values.

Do not immediately change the zone again.

Step 6: Review TTL and caching

Check the TTL associated with the record and consider when the previous value was published.

Remember that lowering the TTL after a change does not necessarily clear a cache entry created under the previous TTL.

Allow the relevant cached information to expire.

Step 7: Test zone health and DNSSEC

If the issue involves delegation, nameserver consistency or zone structure, use IntoDNS or Zonemaster.

If DNSSEC is involved, use DNSViz or Verisign DNSSEC Debugger.

Step 8: Investigate the service beyond DNS

If DNS returns the correct destination, test the server and application.

Check network reachability, web server status, firewall rules, TLS certificates, reverse proxies and application logs.

Do not continue changing DNS records when the evidence points to a server-side problem.

Step 9: Make an authorised correction

Once the cause is identified, document the proposed change and obtain the required approval.

For business-critical domains, the change record should include the original value, the new value, the reason for the change, the person responsible and the time of implementation.

Step 10: Verify and document the result

Repeat the relevant DNS checks and test the actual service from an external network.

For email, send and receive test messages.

For a website, confirm that the correct application loads and that the TLS certificate is valid.

For an application subdomain, test the actual user workflow.

Record the final configuration and keep the evidence with the change documentation.

This process helps distinguish a successful DNS correction from a change that merely makes one test result look correct.

11. Final verdict: which DNS check tool should you choose?

The 20 tools reviewed in this guide cover different parts of DNS administration.

Some are excellent for quick lookups, others are designed for complex diagnostics, and some provide monitoring or performance information.

There is no reason to force one tool into every role.

A well-organised IT team should select a small group of services that complement each other.

Best overall: Google Admin Toolbox Dig

Our overall recommendation

Google Admin Toolbox Dig is the strongest general-purpose starting point in this selection.

It is accessible, free and useful for checking common DNS records.

It is particularly appropriate for administrators who need a quick, reliable way to inspect DNS responses without installing software.

Best for DNS propagation: DNSChecker

DNSChecker is the recommendation for users who need a visual comparison of DNS responses across selected locations.

It is especially useful after changing A, AAAA, MX, NS, CNAME or TXT records.

Its main limitation is that it provides a sample of resolver responses rather than a guarantee of global propagation.

Best for email diagnostics: MXToolbox

MXToolbox is the strongest option for administrators responsible for business email.

Its coverage of MX, SPF, DKIM and DMARC makes it particularly useful during email migrations and delivery investigations.

It should be part of the toolkit for anyone who manages business email domains.

Best for DNS health: Zonemaster

Zonemaster is the recommendation for structured DNS zone testing, especially before a domain migration or delegation change.

Its testing approach is particularly valuable when the team needs to validate a zone before it becomes publicly authoritative.

Best for DNSSEC: DNSViz

DNSViz is the preferred option for investigating DNSSEC relationships and visualising the chain of trust.

For administrators who manage signed DNS zones, it provides technical detail that a conventional record lookup cannot offer.

Best for DNS change monitoring: DNS Spy

DNS Spy is a suitable choice when the organisation needs visibility into changes to important DNS records.

It addresses an operational requirement that manual lookups cannot meet: identifying unexpected changes after the original configuration has been verified.

Best for DNS performance: DNSPerf

DNSPerf is the recommendation for comparing resolver and authoritative DNS performance across its measurement locations.

GRC DNS Benchmark is a useful companion when the administrator wants to compare resolver behaviour from a specific office or network.

Best for internet standards: Internet.nl

Internet.nl is particularly useful for organisations that want to assess DNSSEC, IPv6, HTTPS and email standards in a broader technical review.

Best for security reconnaissance: DNSdumpster

DNSdumpster is a useful option for authorised external asset discovery.

It helps security teams investigate publicly visible hostnames and infrastructure associated with a domain.

Best for service availability: UptimeRobot

UptimeRobot complements DNS diagnostics by monitoring whether public websites and services respond.

It is not a substitute for a DNS health checker, but it helps detect incidents that require investigation.

Our recommended toolkit for a professional IT department

For an organisation that manages websites, email, cloud services and several business domains, the following combination provides a practical starting point:

Operational requirementRecommended tool
Daily DNS record verificationGoogle Admin Toolbox Dig
Propagation checksDNSChecker
Email configurationMXToolbox
DNS health and delegationZonemaster
DNSSEC investigationDNSViz
Record-change monitoringDNS Spy
Resolver performanceGRC DNS Benchmark
Global DNS performance researchDNSPerf
Website availabilityUptimeRobot
Internet standards reviewInternet.nl


This selection avoids unnecessary overlap.

Each tool has a defined purpose, and together they cover the most common DNS tasks in a professional environment.

The final recommendation

The most important part of DNS management is not the number of tools an administrator uses.

It is the quality of the process behind them.

A reliable DNS operation starts with a documented zone, controlled access to the registrar and DNS provider, an inventory of critical records and a clear change procedure.

When something fails, the administrator should establish whether the problem lies with the authoritative configuration, recursive caching, DNSSEC, network connectivity or the destination service.

The Best DNS Check Tools make that work faster and more accurate, but the results still need to be interpreted correctly.

Use a lookup tool to verify records, a propagation checker to compare resolver responses, a health checker to examine zone configuration and monitoring to detect changes over time.

For most IT teams, Google Admin Toolbox Dig, DNSChecker, MXToolbox, Zonemaster and DNSViz provide a strong foundation.

Add DNS Spy and UptimeRobot when ongoing operational visibility becomes important.

That combination is more useful than relying on a single checker and hoping it can explain every DNS problem.


Frequently Asked Questions

What is the best DNS checker?
There is no single tool that is best for every DNS task. Google Admin Toolbox Dig is a good starting point for individual record lookups. DNSChecker and WhatsMyDNS are useful for comparing propagation across selected locations. MXToolbox is particularly useful for email diagnostics, while DNSViz and Verisign DNSSEC Debugger are more appropriate for DNSSEC investigations.

For a general DNS health review, IntoDNS and Zonemaster are useful options.
Are DNS check tools free?
Several of the tools in this guide offer free checks or publicly accessible utilities. However, some providers reserve advanced monitoring, bulk checks, APIs, historical reporting or additional features for paid plans.

Always check the current service terms and feature limits before adopting a tool for business use.
How do I check whether DNS has propagated?
Enter the domain in DNSChecker or WhatsMyDNS, select the record type you changed and compare the returned values from the displayed locations.

Then verify the authoritative name servers. If they publish the expected value but some recursive resolvers return an older answer, caching may explain the difference.

Remember that propagation checkers sample selected resolvers. They do not test every DNS server on the internet.
How long does DNS propagation take?
There is no single propagation time that applies to every DNS change.

The TTL of the previous record, resolver caching behaviour, the type of change and the authoritative DNS configuration all influence when users receive the new answer.

A low TTL may allow cached values to expire sooner, but changing the TTL after a resolver has already cached the old value does not necessarily shorten that existing cache entry.
Can I force DNS propagation?
No. A domain owner cannot force every recursive resolver on the internet to discard its cached data immediately.

You can plan changes by lowering TTL values in advance, publishing the correct information on authoritative servers and waiting for existing cache entries to expire.

You can also clear local DNS caches on devices you control, but that only affects those devices. It does not clear the caches maintained by external ISPs or public DNS providers.
Why does my domain work on mobile data but not on office Wi-Fi?
The two networks may use different DNS resolvers or have different cached answers.

Check the domain through DNSChecker and compare the results with a public resolver. Also check the office router, firewall or internal DNS server.

Corporate networks may use internal DNS zones, filtering systems or forwarding rules that affect resolution. If the public domain resolves correctly but office users still experience problems, investigate the internal DNS configuration.
Why does my website still show the old server after I changed the A record?
The old address may still be cached by a recursive resolver, or the authoritative DNS zone may not have been updated as expected.

First, inspect the A record returned by the authoritative name servers. Then compare it with responses from different resolvers.

If the authoritative answer is still old, check whether you edited the active DNS provider and the correct zone. If the authoritative answer is new but selected resolvers return the old value, caching is a likely explanation.
Does DNS propagation affect email?
Yes. Changes to MX records can affect where new messages are delivered.

If an organisation changes email providers, some sending systems may continue to use cached MX information for a period. This is why email migrations should include a transition plan and tests for both inbound and outbound mail.

Also check SPF, DKIM and DMARC. These records influence email authentication and are separate from the MX record used for mail routing.
How do I check MX records?
Use MXToolbox, Google Admin Toolbox Dig or NSLookup.io. Select an MX lookup or inspect the MX record directly.

Compare the returned hostnames and priorities with the official values supplied by the organisation's email provider.
How do I check TXT records?
Use Google Admin Toolbox Dig, NSLookup.io or another DNS lookup service and select TXT as the record type.

TXT records may contain domain verification values, SPF policies and other service configuration data. If the domain has several TXT records, inspect each relevant value rather than assuming that the first result represents the entire configuration.
How do I know which nameservers my domain uses?
Check the domain's NS records using a DNS lookup service. You can also inspect the nameserver delegation at the registrar where the domain is registered.

The important point is to distinguish between the nameservers displayed in a DNS provider's control panel and the nameservers actually delegated by the registrar. They should correspond to the provider responsible for the active zone.
What is the difference between a DNS lookup and a propagation check?
A DNS lookup asks a resolver for a particular record and displays the response.

A propagation check compares responses from multiple selected resolvers or locations. It helps identify differences after a change.

Neither operation automatically provides a complete health audit of the domain.
What is the difference between authoritative and recursive DNS?
An authoritative DNS server holds the DNS records for a zone and provides authoritative answers for that zone.

A recursive resolver obtains answers on behalf of clients. It may query authoritative servers and cache the results so that subsequent requests can be answered more quickly.

This distinction is essential when troubleshooting. The authoritative server may already publish the new value while a recursive resolver continues to return an older cached answer.
Can DNS check tools identify a hacked domain?
They can help identify unexpected records, suspicious destinations, unusual nameserver changes or other signs that deserve investigation.

However, a DNS lookup alone cannot establish that a domain has been hacked. A proper investigation should include registrar and DNS provider access logs, account security, change history and other relevant evidence.
Advertisement

Liked this? Get the next one in your inbox