Free DNS Checker · India · No Login Required
DNS Checker
–
Check my DNS, MX record, cname record, & a records
Verify A, MX, CNAME, NS, TXT, AAA records across India and 20 global locations.
Enter domain to check DNS
Enter your domain name without www or https
After changing hosts, enter the new IP your provider gave you. We’ll show which locations have switched over (green) and which still serve the old one (red).
Checking DNS propagation worldwide…
Free DNS checker tool
Check DNS online – Built in India
check DNS online using this tool and get the likely root cause when something’s off, and the exact steps to fix it and not just a grid of green and red dots.
Whether you’ve just migrated hosts, you’re troubleshooting a site, or you’re reviewing your setup, the tool tailors its guidance to your situation.
🔍
DNS Lookup Tool
Check A, MX, CNAME, NS, TXT, AAAA records for any domain — Mumbai results in under 2 seconds
📡
DNS Propagation Checker
Verify your nameserver changes have propagated worldwide after a migration
📧
MX Record Check
Check your mail server records to confirm email is being delivered correctly
🔗
CNAME Checker
Verify CNAME aliases point to correct destinations for www and subdomain setup
🖥️
Check DNS Server
Verify nameservers are authoritative and responding correctly for your domain
Free DNS checker, built in India
What makes this DNS lookup tool different
Most DNS lookup tools show green and red dots, then leave you to interpret them. This one reads the same result and tells you what’s happening, why, and what to do.
A typical DNS checker shows
5 green, 3 red. Now what?
↓
This DNS checker adds
Verdict: 62% propagated — normal migration lag, not an error.
The 3 red locations update within your TTL window (~4 hrs). Your authoritative
nameserver already has the correct record.
1
VerdictWhat state your DNS is really in.
2
ContextYour TTL, host & nameserver, explained.
3
Root causePropagation, nameserver, DNSSEC or migration.
4
Next stepsTailored to your situation, not generic.
It even asks why you’re here — so the fix fits your situation:
Just migrated
Fixing a problem
Just checking
Pick one and you get resolution steps for that path — not a one-size-fits-all checklist.
DNS troubleshooting guide
DNS not working after migration? Diagnose and fix it
If your website is showing old IP after migration, nameserver is not updating, email not working after DNS change India, or your domain is not resolving after a hosting change — this section diagnoses every common scenario with a specific fix for each.
Common browser DNS error messages explained
These error messages in Chrome, Firefox, and Edge all indicate a DNS problem. Use the DNS checker above to diagnose which specific record is causing the error.
DNS_PROBE_FINISHED_NXDOMAIN
DNS server returned “Non-Existent Domain.” The domain name cannot be found in DNS. Usually means: nameservers changed but DNS zone not configured on new host, or domain has expired.
Fix: Check NS records above → verify DNS zone exists on new host
ERR_NAME_NOT_RESOLVED
Chrome’s equivalent of NXDOMAIN. The domain could not be resolved to an IP address. Often caused by incorrect nameservers, deleted DNS records, or domain expiry.
Fix: Check A record above → if no result, DNS zone is empty or missing
Server IP address could not be found
Browser could not get an IP for the domain. Nameservers may be responding but returning empty results. Common after migrating nameservers before configuring records on the new host.
Fix: Log into new host → Add Domain → create A record manually
DNS Server Not Responding
Your device’s DNS server is unreachable or not responding. Usually a local network issue, not your domain’s problem. First check: can you open other websites? If yes, it is your domain.
Fix: Switch device DNS to 8.8.8.8 → retry → use checker above to confirm
is my website DNS working?
If you are asking this after a migration and the site looks fine in your browser — use the checker above. Your local DNS cache may show the new host while other visitors still see the old one.
Check: Run A record check above → compare Mumbai result with your browser
Why is my domain not loading?
Four causes: (1) DNS propagation in progress, (2) DNS zone not configured on new host, (3) Domain expired, (4) CNAME conflict on root domain. Check NS and A records above to narrow it down.
Diagnose: Check NS first (nameservers correct?), then A (IP returning?)
Common DNS migration problems — with India-specific fixes
Most Common
Website showing old IP after migration
What happens: You changed nameservers or A records but the old website still loads. Run the DNS checker above — if it shows different IPs in different locations, propagation is actively in progress.
Why it persists: Your previous TTL value determines how long DNS servers cache the old record. TTL 86400 = 24-hour wait. TTL 300 = 5-minute wait. Check the TTL shown in your results — that is your maximum wait time.
India-specific: BSNL caches for the full TTL duration. Jio and Airtel typically update in 4–12 hours even with high TTL. If you see the new IP from the above checker but still see the old site in your browser — flush your local DNS cache.
2. Windows flush:
3. Chrome flush: chrome://net-internals/#dns → Clear
4. If not yet showing new IP, wait the TTL duration shown
Re-run the check above once your TTL window has passed to confirm propagation is complete.
Why it persists: Your previous TTL value determines how long DNS servers cache the old record. TTL 86400 = 24-hour wait. TTL 300 = 5-minute wait. Check the TTL shown in your results — that is your maximum wait time.
India-specific: BSNL caches for the full TTL duration. Jio and Airtel typically update in 4–12 hours even with high TTL. If you see the new IP from the above checker but still see the old site in your browser — flush your local DNS cache.
Fix steps
1. Check A record above — if showing new IP, propagation complete2. Windows flush:
ipconfig /flushdns3. Chrome flush: chrome://net-internals/#dns → Clear
4. If not yet showing new IP, wait the TTL duration shown
Critical
Nameserver not updating India after 48 hours
What happens: NS record check shows your old nameservers even after 48+ hours. Propagation should be complete by now — something went wrong at the registrar level.
Most common cause: Indian domain registrars (BigRock, GoDaddy India, Namecheap) often require a separate Save or Confirm step that is easy to miss. The nameserver fields accept and display new values without actually saving them until you click a specific confirmation button.
Secondary cause: Some registrars require email verification for nameserver changes. Check for a verification email from your registrar.
2. DNS/Nameserver settings → check for unsaved changes
3. Re-enter the new nameservers and look for a Save/Submit button
4. Check email for registrar verification request
5. Wait 24 hours after re-saving, check NS above again
After re-saving, use the NS check above to confirm the new nameservers have taken effect.
Most common cause: Indian domain registrars (BigRock, GoDaddy India, Namecheap) often require a separate Save or Confirm step that is easy to miss. The nameserver fields accept and display new values without actually saving them until you click a specific confirmation button.
Secondary cause: Some registrars require email verification for nameserver changes. Check for a verification email from your registrar.
Fix steps
1. Log back into your registrar2. DNS/Nameserver settings → check for unsaved changes
3. Re-enter the new nameservers and look for a Save/Submit button
4. Check email for registrar verification request
5. Wait 24 hours after re-saving, check NS above again
Email Issue
Email not working after DNS change India
What happens: Website loads correctly on new host but emails are bouncing or not arriving. This is an MX record not propagating issue or missing MX configuration on the new nameserver.
Why it happens: When you changed nameservers, your MX records moved to the new DNS provider’s control. If MX records were not manually recreated there, email routing breaks immediately.
Run this check now: Select MX in the DNS checker above, enter your domain. Compare results to your email provider’s required MX values below.
Zoho Mail:
Microsoft 365:
cPanel hosting email:
Why it happens: When you changed nameservers, your MX records moved to the new DNS provider’s control. If MX records were not manually recreated there, email routing breaks immediately.
Run this check now: Select MX in the DNS checker above, enter your domain. Compare results to your email provider’s required MX values below.
Required MX records by email provider
Google Workspace: aspmx.l.google.com (P1)Zoho Mail:
mx.zoho.in (P10)Microsoft 365:
domain.mail.protection.outlook.comcPanel hosting email:
mail.yourdomain.com
After recreating your MX records, re-check with MX selected above to confirm they’re live.
MX Record
MX record not propagating India
What happens: You added or updated MX records but email still routes to the old server. Check MX record above — if TTL shown is 86400, DNS servers will hold the old MX for up to 24 hours.
India ISP behaviour: Airtel’s DNS resolver routes to Singapore (APNIC research, Dec 2024), meaning Airtel users may see old MX records longer than other ISPs. Ask senders to retry after 12 hours if their email bounces — Airtel’s cache may not have updated yet.
Verify SPF too: Even with correct MX, emails go to spam without a valid SPF TXT record. Select TXT above and check for an SPF record starting with
2. TXT check → verify SPF record exists
3. If MX correct but email still fails → check DKIM TXT
4. Wait TTL duration then recheck
More email DNS troubleshooting in FAQ →
India ISP behaviour: Airtel’s DNS resolver routes to Singapore (APNIC research, Dec 2024), meaning Airtel users may see old MX records longer than other ISPs. Ask senders to retry after 12 hours if their email bounces — Airtel’s cache may not have updated yet.
Verify SPF too: Even with correct MX, emails go to spam without a valid SPF TXT record. Select TXT above and check for an SPF record starting with
v=spf1.
MX record troubleshooting
1. MX check above → confirm correct values returned2. TXT check → verify SPF record exists
3. If MX correct but email still fails → check DKIM TXT
4. Wait TTL duration then recheck
Critical
Domain not resolving after hosting change
What happens: Domain returns NXDOMAIN or “server IP address could not be found” immediately after changing hosting. The DNS checker above shows no records at all.
Most common cause: Nameservers were changed to new host’s nameservers, but the DNS zone (the collection of A, MX, CNAME records) was not created on the new host. The nameservers are authoritative but have nothing to serve.
How to fix: Log into your new host’s control panel and find “Add Domain” or “Addon Domain” or “DNS Zone.” Create the zone for your domain and add at minimum an A record pointing to your new server’s IP address.
Cloudways: Application → Domain Management → Add Domain
cPanel: Zone Editor → +A Record → enter IP
BigRock: Hosting CP → Domain Manager → DNS Records
Once you’ve created the zone, re-run the check above to confirm records are now resolving.
Most common cause: Nameservers were changed to new host’s nameservers, but the DNS zone (the collection of A, MX, CNAME records) was not created on the new host. The nameservers are authoritative but have nothing to serve.
How to fix: Log into your new host’s control panel and find “Add Domain” or “Addon Domain” or “DNS Zone.” Create the zone for your domain and add at minimum an A record pointing to your new server’s IP address.
Platform-specific fix
Hostinger hPanel: Domains → Manage → DNS Zone EditorCloudways: Application → Domain Management → Add Domain
cPanel: Zone Editor → +A Record → enter IP
BigRock: Hosting CP → Domain Manager → DNS Records
ISP Issue
DNS propagated but Airtel/BSNL still show old site
What happens: The DNS checker above shows new IP from Mumbai. You can see the new site. But visitors on Airtel or BSNL still see the old site days later.
Why it happens: Airtel routes DNS to Singapore (slower propagation). BSNL has 24–48 hour cache times. These ISPs hold old records much longer than Jio. This is not something you can fix on your end — it resolves with time.
Workaround for urgent cases: Tell Airtel/BSNL users to manually change their device DNS to 8.8.8.8 or 1.1.1.1. This bypasses the ISP DNS entirely and they immediately see the propagated result.
iPhone: Settings → Wi-Fi → (i) → Configure DNS → 8.8.8.8
Windows: Network → DNS → Preferred: 8.8.8.8
India ISP propagation timeline →
Why it happens: Airtel routes DNS to Singapore (slower propagation). BSNL has 24–48 hour cache times. These ISPs hold old records much longer than Jio. This is not something you can fix on your end — it resolves with time.
Workaround for urgent cases: Tell Airtel/BSNL users to manually change their device DNS to 8.8.8.8 or 1.1.1.1. This bypasses the ISP DNS entirely and they immediately see the propagated result.
Visitor workaround
Android: Settings → Wi-Fi → Modify → DNS → 8.8.8.8iPhone: Settings → Wi-Fi → (i) → Configure DNS → 8.8.8.8
Windows: Network → DNS → Preferred: 8.8.8.8
India ISP propagation data
DNS propagation checker – India ISP timeline
DNS propagation for major Indian ISPs typically takes 2 to 48 hours. Major ISPs, such as Jio (AS55836), Airtel (AS9829), Vodafone Idea (AS24560), and BSNL (AS9829) – often cache records significantly beyond their set TTL limits, making regional(India) propagation one of the slowest in the global chain.
This table tells you what to expect for each Indian ISP after migration.
DNS speed test – how quickly your DNS responds to Indian visitors
Website owners are discovering that slow DNS resolution is a hidden cause of slow page loading that no amount of hosting speed improvement can fix, because DNS happens before your hosting server is even contacted.
⚡ What is DNS speed and why does it matter?
Every time a visitor loads your website, their browser first asks a DNS server: “What IP address is this domain?” The time this lookup takes is your DNS resolution time – also called DNS latency.
Most of that delay comes down to distance. According to Google’s Public DNS documentation, latency between a user and their resolver is driven largely by the geographical distance between them, along with network congestion and routing. So a resolver located in India responds faster for your Indian visitors than one routed through the US or Europe
How to test your DNS speed from India
Method – Command line
Windows:
Linux/Mac:
Windows:
nslookup yourdomain.com 1.1.1.1Linux/Mac:
dig yourdomain.com @1.1.1.1Run it a couple of times: the first includes connection setup, and later runs show the cached, steady-state speed. Under 50ms is excellent; consistently over 200ms suggests your DNS provider may be routing through distant servers, and one with Indian infrastructure would resolve faster for your visitors.
If your DNS server is in US, this lookup takes 200 – 500ms. If it uses a provider with a Mumbai edge node, like Cloudflare, it takes under 10ms. That difference adds up on every page, for every visitor – completely invisible to your users, but directly affecting how fast your site feels.
This is also why your DNS and hosting location matters: A provider with real Indian Server infrastructure resolves faster for your Indian visitors than one routing through the US or Europe – which is exactly what our Partner Host Latency – India hosting benchmarks measures.
What is TTL?
Time To Live
The number of seconds DNS servers cache your records. Low TTL = changes propagate fast. High TTL = fewer lookups during normal operation.
Before migration
300 seconds (5 min)
Lower your TTL to 300 at least 24–48 hours before migrating. Once it’s low, changes become visible within minutes instead of hours.
After migration
3,600 seconds (1 hr)
Raise TTL back once migration completes, to reduce unnecessary DNS lookups during normal operation.
You change TTL in your DNS provider’s control panel, on each record or the zone default.
🔗 DNS speed in your total page load from India
DNS Lookup8-280ms varies by visitor’s resolver
→
TCP Connect10-50ms Server location
→
TLS Handshake50-600ms SSL + server
→
TTFB195-623ms Host performance
→
Page Loaded1–8 sec Total experience
DNS resolution is the first step and happens before your server is contacted – a small but often-overlooked part of total load time.
Test your full page speed from Mumbai →
DNS record types explained
Check DNS records – what each type does for your website
Every domain has multiple DNS record types. Each controls a different part of how your website, email, and subdomains work. Here is when to check each one — and what to do when it is wrong.
A
Address Record
Your website’s IP address
Maps your domain to your hosting server’s IPv4 address. This is the first record to check when your website is showing old IP after migration. If the A record shows your old host’s IP, DNS has not yet propagated.
Check A record when: Site unreachable after migration, or website showing old host after changing nameservers
MX
Mail Exchange — MX Record Check
Controls email delivery for your domain
An MX record check tells you which mail server receives email for your domain. Wrong MX = bounced emails. After any hosting migration, this is the second record to check. For Google Workspace:
MX record check when: Email not working after DNS change, or emails going to spam
aspmx.l.google.com at priority 1.CN
Canonical Name — CNAME Checker
Domain alias for subdomains
A CNAME checker verifies subdomain aliases point to the correct destination. Used for www setup, connecting Shopify or Mailchimp subdomains, and Google Workspace verification. Note: CNAME cannot coexist with A or MX on the same name — a common cause of domain not resolving after hosting change.
CNAME checker when: www not loading, subdomain not connecting to a service, post-migration misconfiguration
NS
Nameserver Check
Who controls your DNS
A nameserver check tells you which DNS servers are authoritative for your domain. After changing hosting, check this first. If NS records still show your old registrar’s nameservers after 48 hours, your registrar may not have saved the change. Verify the update was applied.
Nameserver check when: Domain not resolving after hosting change, MX or A records returning wrong values
TXT
Text Record — DNS Name Check
SPF, DKIM, domain verification
TXT records (also called DNS name check records) store SPF (email authentication), DKIM signatures, and Google Search Console verification. If emails from your domain go to spam after a DNS change, check TXT for a missing SPF record. SPF format:
DNS name check when: Emails going to spam, Google Search Console verification failing, DKIM authentication errors
v=spf1 include:youresp.com ~allAAAA
IPv6 Address Record
IPv6 address for Jio/mobile users
he IPv6 equivalent of an A record. Jio has extensive IPv6 deployment, so an AAAA record lets Jio users connect over IPv6 directly. Without one, they fall back to your IPv4 (A record) — modern devices handle this fallback smoothly, so it’s rarely a problem, but having both gives you complete coverage.On most modern managed hosting, AAAA records are configured automatically.
Check AAAA when:you want to confirm full IPv6 coverage, or mobile users report IPv6-specific connectivity issues.
Frequently asked questions
DNS checker questions answered for Indian websites
Plain answers – no jargon, no technical assumptions about your background.
How do I check my DNS online free from India?
+Enter your domain in the DNS checker tool at the top of this page and click Check DNS. Select your record type – A for website IP, MX for email, NS for nameservers, CNAME for subdomains, TXT for SPF/DKIM. Results come from our HG Node, Mumbai server via DNS-over-HTTPS in under 5 seconds. Completely free, no login required. This is the most accurate way to check DNS online from India because it uses a real Mumbai server, not a US-hosted tool with an “India” label.
How do I check DNS speed test from India?
+This tool checks your DNS records and propagation, not DNS speed test directly. To measure your domain’s actual DNS resolution time, use the command line: on Windows run nslookup yourdomain.com, or on Mac/Linux run dig yourdomain.com and check the ‘Query time’ in the output.
Run it twice – the first includes setup, the second shows the cached, steady-state speed. Under 50ms is excellent; consistently over 200ms suggests your DNS provider may be routing through distant servers, and one with Indian infrastructure would resolve faster for your visitors.
Run it twice – the first includes setup, the second shows the cached, steady-state speed. Under 50ms is excellent; consistently over 200ms suggests your DNS provider may be routing through distant servers, and one with Indian infrastructure would resolve faster for your visitors.
What is a free alternative to MXToolbox DNS lookup for Indian websites?
+MXToolbox DNS lookup checks from US-based servers – It isn’t focused on India-specific propagation. For Indian webmasters, this matters because Indian ISPs (Jio, Airtel, BSNL) may cache completely different values than US DNS resolvers, especially during the 4–48 hour propagation window after a migration.
Hosting Garage DNS checker is the India-native alternative to MXToolbox DNS lookup – checking A, MX, CNAME, NS, TXT, and AAAA records from our HG Node, Mumbai based private server. It shows what your Indian visitors actually see, not what a US resolver sees. Free, no login, no usage limits.
For MX record checks specifically – MXToolbox’s primary use case – our MX record check returns results from Mumbai that reflect Indian mail server routing.
Hosting Garage DNS checker is the India-native alternative to MXToolbox DNS lookup – checking A, MX, CNAME, NS, TXT, and AAAA records from our HG Node, Mumbai based private server. It shows what your Indian visitors actually see, not what a US resolver sees. Free, no login, no usage limits.
For MX record checks specifically – MXToolbox’s primary use case – our MX record check returns results from Mumbai that reflect Indian mail server routing.
How do I check DNS propagation in India?
+Enter your domain in the DNS propagation checker above and select A records (for website) or NS records (for nameservers). The result shows what your domain currently resolves to from India. For migration tracking: note the IP shown immediately after changing hosts. Check every 1–2 hours. When the IP matches your new host’s IP, propagation is complete for Indian visitors.
Propagation timeline by ISP: Jio = 2–6 hours, Airtel = 4–24 hours, ACT = 2–8 hours, BSNL = 24–48 hours. To speed up future migrations, lower your TTL to 300 seconds at least 24 hours before making any DNS changes. The DNS propagation checker will then show changes within minutes rather than hours.
Propagation timeline by ISP: Jio = 2–6 hours, Airtel = 4–24 hours, ACT = 2–8 hours, BSNL = 24–48 hours. To speed up future migrations, lower your TTL to 300 seconds at least 24 hours before making any DNS changes. The DNS propagation checker will then show changes within minutes rather than hours.
How do I check DNS server and verify nameservers are correct?
+To check DNS server settings for your domain, select NS from the record type dropdown in the DNS checker above. The result shows your current authoritative nameservers. If these do not match your new host’s nameservers, your DNS is still pointing to the old host.
For Hostinger: nameservers should be ns1.dns-parking.com and ns2.dns-parking.com. For Cloudways: the nameservers shown in your Application → Domain Management panel. For cPanel hosts: typically ns1.yourhostingprovider.com and ns2.yourhostingprovider.com.
If NS check shows wrong nameservers after 48 hours, log back into your domain registrar and verify the change was saved. Many Indian registrars require a separate confirmation step.
For Hostinger: nameservers should be ns1.dns-parking.com and ns2.dns-parking.com. For Cloudways: the nameservers shown in your Application → Domain Management panel. For cPanel hosts: typically ns1.yourhostingprovider.com and ns2.yourhostingprovider.com.
If NS check shows wrong nameservers after 48 hours, log back into your domain registrar and verify the change was saved. Many Indian registrars require a separate confirmation step.
How do I do a DNS name check for TXT records?
+A DNS name check typically refers to checking TXT records – which store SPF email authentication, DKIM signatures, Google Search Console verification codes, and domain ownership proof for services like Cloudflare and Shopify. Select TXT from the record type dropdown above.
Common DNS name check scenarios in India:
• Google Search Console verification failing: TXT record not saved or propagated
• Emails going to spam: SPF record missing – should start with v=spf1
• Emails bouncing: DKIM TXT record missing or incorrect after migration
• New hosting migration: verify old host’s verification records were removed and new ones added
After adding or changing TXT records, use this DNS name check tool every 30 minutes to confirm propagation progress.
Common DNS name check scenarios in India:
• Google Search Console verification failing: TXT record not saved or propagated
• Emails going to spam: SPF record missing – should start with v=spf1
• Emails bouncing: DKIM TXT record missing or incorrect after migration
• New hosting migration: verify old host’s verification records were removed and new ones added
After adding or changing TXT records, use this DNS name check tool every 30 minutes to confirm propagation progress.
How do I check domain owner and when does my domain expire?
+To check domain owner and expiry date, use a WHOIS lookup at who.is or lookup.icann.org – enter your domain name and look for “Registrant Name” and “Registry Expiry Date.” Our DNS checker shows NS records which reveal your current registrar.
For a domain expiry check: the expiry date is in the WHOIS “Registry Expiry Date” field.
Critical: domain expiry and hosting expiry are completely separate. Your domain can expire while hosting is active (site goes offline) or hosting can expire while domain is active (site goes offline for different reasons). Check both independently.
For a domain expiry check: the expiry date is in the WHOIS “Registry Expiry Date” field.
Critical: domain expiry and hosting expiry are completely separate. Your domain can expire while hosting is active (site goes offline) or hosting can expire while domain is active (site goes offline for different reasons). Check both independently.
What does DNS_PROBE_FINISHED_NXDOMAIN mean and how do I fix it?
+DNS_PROBE_FINISHED_NXDOMAIN means “Non-Existent Domain” – the DNS server cannot find any records for your domain. This is different from a server error – the DNS lookup itself returned a definitive “this domain does not exist” response.
Common causes and fixes:
• Nameservers changed to new host but DNS zone not created on new host → log into new host, Add Domain, create A record
• Domain has expired → check with registrar immediately, renew + wait propagation
• Typo in domain name → verify the domain is spelled correctly
• DNS record deleted accidentally → restore from registrar backup or recreate
Use the NS record check above first – if it returns results, your nameservers are working but the new host has no records configured. If it returns nothing, your domain registrar-level configuration may be the issue.
Common causes and fixes:
• Nameservers changed to new host but DNS zone not created on new host → log into new host, Add Domain, create A record
• Domain has expired → check with registrar immediately, renew + wait propagation
• Typo in domain name → verify the domain is spelled correctly
• DNS record deleted accidentally → restore from registrar backup or recreate
Use the NS record check above first – if it returns results, your nameservers are working but the new host has no records configured. If it returns nothing, your domain registrar-level configuration may be the issue.
Is this DNS checker free to use?
+Yes – completely free, no login, no registration, no usage limits. You can check any domain, any record type (A, MX, CNAME, NS, TXT, AAAA), as many times as needed. Hosting Garage DNS checker runs from HG Node, our Mumbai server via DNS-over-HTTPS, providing genuine India-origin DNS resolution data.
Our tools are completely independent and will remain free.
Our tools are completely independent and will remain free.
Why does my DNS check show a DNSSEC or SERVFAIL error?
+SERVFAIL means a validating resolver – like Google DNS — refused to return your records. The most common cause is a broken DNSSEC configuration: the resolver expects cryptographic signatures that are missing or invalid, so it won’t resolve the domain at all. When this happens, visitors using that resolver genuinely can’t reach your site, while those on non-validating resolvers still can. If you recently disabled DNSSEC, this usually clears within 24–48 hours as cached DS records expire. If it persists, check that the DS record has been fully removed at your domain registrar. This checker flags DNSSEC failures specifically, rather than showing a generic error – so you know it’s a security-chain issue, not simple propagation lag.
Why do different DNS checkers show different results for the same domain?
+Two reasons. First, different tools query different resolvers, and each resolver caches records on its own schedule – so during propagation, one may have your new record while another still serves the old one. Second, for geographically-routed domains, results depend on EDNS Client Subnet, so tools checking from different locations can legitimately get different answers. And if DNSSEC validation is involved, a strict resolver may refuse to resolve a domain that a lenient one returns fine. None of these mean a tool is broken – they reflect the genuinely distributed nature of DNS.
Indian Hosting providers Performance data
Check web hosting India performance
Your DNS is sorted – but is the server behind it fast? Here’s how it compares on real response time, measured from India. Useful whether you’ve just migrated or you’re deciding where to move next.
Source:TTFB: 90-day average from HetrixTools Mumbai monitoring from Host Latency. Affiliate disclosure: plan links earn us a small commission at no extra cost to you — rankings are based solely on performance data.
Check Full Hosting Report Card with 90-day uptime monitoring →
Hosting Garage Research Team
Reviewed
Built by people with 13+ years of hands-on experience in the Indian web hosting industry - including those who've handled DNS migrations and propagation issues. We explain what a result means, its root cause and how to fix it.
Two more checks worth a minute
DNS checked – now see your full website health
Run a full website health check →
SSL, DNS, security and speed in one scan – diagnosed, explained, and with the fixes that matter.
Test your website speed →
See real page load time and server response from India — the full picture beyond DNS.