Skip to content

ERR_DNS_MALFORMED_RESPONSE

Key idea:

ERR_DNS_MALFORMED_RESPONSE — Chrome DNS resolver received a response that does not conform to DNS wire format. Causes: upstream resolver bug (rare), DNSSEC validation failure, DoH (DNS-over-HTTPS) endpoint serving HTML error page instead of DNS response, DNS poisoning attempts. Fix: change DNS provider or disable DoH.

Below: causes, fixes, FAQ.

Check your site's SSL →

Common Causes

  • DoH endpoint (1.1.1.1/dns-query) returning 503 HTML instead of DNS
  • DNSSEC validation failure — upstream stripped DS/RRSIG records
  • Cached response with DNSSEC mismatch
  • DNS poisoning attempt (rare)
  • Browser-level resolver bug (specific Chrome version)

Step-by-Step Fix

  1. chrome://settings/security → disable "Use secure DNS"
  2. Try other DoH provider: Google 8.8.8.8/dns-query, Quad9 9.9.9.9
  3. Flush DNS: chrome://net-internals/#dns → Clear host cache
  4. Windows: ipconfig /flushdns; macOS: dscacheutil -flushcache
  5. Check domain DNSSEC: Enterno DNS checker

Check SSL Certificate →

Related SSL Errors

TL;DR: Fixing ERR_DNS_MALFORMED_RESPONSE

The ERR_DNS_MALFORMED_RESPONSE error occurs when a browser receives an invalid DNS reply, often due to misconfigured DNS settings or server responses. To resolve this issue, check your DNS configuration, clear your browser cache, and use tools like nslookup or dig to troubleshoot DNS queries. Ensure your DNS servers are responsive and correctly configured.

Understanding ERR_DNS_MALFORMED_RESPONSE

The ERR_DNS_MALFORMED_RESPONSE error indicates that the DNS response received by the browser is malformed or not compliant with DNS standards. This can occur for several reasons, including:

  • Misconfigured DNS records.
  • Issues with the DNS server responding incorrectly.
  • Corrupted browser cache or DNS cache.

When a browser sends a DNS request, it expects a well-formed response that adheres to the Domain Name System (DNS) protocols. If the response deviates from expected formats, the browser will trigger this error.

Common symptoms include the inability to access websites, loading delays, and inconsistent connectivity. Depending on the browser and operating system, users may encounter different error messages, but the underlying issue remains the same.

To diagnose the problem, you may consider the following:

  1. Check if the DNS server is reachable using ping or traceroute.
  2. Utilize nslookup or dig commands to examine the DNS records returned for your domain.
  3. Look for discrepancies in the DNS records, such as incorrect IP addresses or missing records.

Practical Steps to Resolve the Issue

To effectively resolve the ERR_DNS_MALFORMED_RESPONSE error, follow these practical steps:

1. Check DNS Configuration

Start by verifying your DNS configuration. If you manage your own DNS server, ensure that it is correctly set up. Use the following command to check your DNS records:

dig example.com ANY

Replace example.com with your domain. Look for any malformed records. You should see a response with properly formatted records.

2. Clear Browser and DNS Cache

Cached data may lead to persistent errors. Clear your browser cache and DNS cache:

  • For Windows, open Command Prompt and run:
ipconfig /flushdns
  • For macOS, use:
sudo killall -HUP mDNSResponder

3. Change DNS Servers

If the problem persists, consider changing your DNS servers. Public DNS servers like Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1) can often resolve these issues more effectively than ISP-provided DNS servers. To change DNS settings:

  1. Open your network settings.
  2. Select your network connection.
  3. Access the properties and find the DNS settings.
  4. Input the new DNS server addresses.

4. Contact Your DNS Provider

If all else fails, reach out to your DNS hosting provider. They can provide insights and support for any underlying issues with their infrastructure.

By following these steps, you can systematically address the ERR_DNS_MALFORMED_RESPONSE error and restore normal browsing functionality.

CertificateExpiry, issuer, domains (SAN)
ChainIntermediate and root CA validation
TLS ProtocolTLS version and cipher suite
VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3
supported
Full
CA chain check
<2s
result
30/14/7
days-to-expiry alerts

How it works

1

Enter domain

2

TLS chain verified

3

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)
  • Confirms domain ownership only
  • Issued in minutes automatically
  • Free via Let's Encrypt
  • Suitable for most websites
  • Most common certificate type
OV / EV
  • Organization (OV) or Extended Validation (EV)
  • Issued in 1-5 business days
  • Costs $50 to $500/year
  • For finance, e-commerce, government sites
  • Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.
Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.
Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.
Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.
Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.
Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.
Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.
Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.
Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Sign up free

Learn more

Sources

Frequently Asked Questions

DoH vs Do53?

DoH (DNS-over-HTTPS): queries over HTTP/2 to resolver. Do53: classic UDP 53. DoH encrypted, private; but middleboxes may interfere.

DNSSEC debug?

dig +dnssec domain. If AD flag set = validated. Otherwise — chain broken somewhere.

Chrome Secure DNS list?

Settings → Security → advanced. Providers: automatic, Cloudflare, Google, Quad9, NextDNS, CleanBrowsing.

Monitor DNS?

<a href="/en/dns">Enterno DNS</a> checks records + DNSSEC validation chain. <a href="/en/monitors">Scheduled monitors</a> alert on DNS changes.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.