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.
Free online tool — DNS lookup tool: instant results, no signup.
ipconfig /flushdns; macOS: dscacheutil -flushcacheThe 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.
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:
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:
ping or traceroute.nslookup or dig commands to examine the DNS records returned for your domain.To effectively resolve the ERR_DNS_MALFORMED_RESPONSE error, follow these practical steps:
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 ANYReplace example.com with your domain. Look for any malformed records. You should see a response with properly formatted records.
Cached data may lead to persistent errors. Clear your browser cache and DNS cache:
ipconfig /flushdnssudo killall -HUP mDNSResponderIf 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:
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.
DNS (Domain Name System) translates domain names into IP addresses. DNS records are instructions that define where to route traffic, email, and how to verify domainownership.
Query all record types — A, AAAA, MX, NS, TXT, CNAME, SOA — in a single request.
Direct queries to authoritative servers. Results in milliseconds, no caching.
SPF, DKIM, and DMARC analysis to evaluate email protection against spoofing and phishing.
Save check results. Compare DNS records before and after registrar changes.
DNS check after deploy
SPF/DKIM/DMARC audit
DNS config audit
DNS zone control
v=spf1 TXT record.DNS check history, API keys and DNS change monitoring.
Sign up freeDoH (DNS-over-HTTPS): queries over HTTP/2 to resolver. Do53: classic UDP 53. DoH encrypted, private; but middleboxes may interfere.
dig +dnssec domain. If AD flag set = validated. Otherwise — chain broken somewhere.
Settings → Security → advanced. Providers: automatic, Cloudflare, Google, Quad9, NextDNS, CleanBrowsing.
Enterno DNS checks records + DNSSEC validation chain. Scheduled monitors alert on DNS changes.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.