Skip to content
https://www.duckduckgo.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.duckduckgo.com/
200https://duckduckgo.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.duckduckgo.com/ https://duckduckgo.com/

Consistent

B
TLS Certificate Expiry & Recommendations
252 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

252
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 42 ms lookup
PASS
1 A records, 42 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.149.246.39
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: duckduckgo.com
Info::
8 nameserver(s) configured
Got: dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns01.quack-dns.com, ns02.quack-dns.com, ns03.quack-dns.com, ns04.quack-dns.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 42 ms
Got: 42 ms
A52.149.246.39
AAAA
CNAMEduckduckgo.com
NSdns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns01.quack-dns.com, ns02.quack-dns.com, ns03.quack-dns.com, ns04.quack-dns.com
MX
0 duckduckgo-com.mail.protection.outlook.com
TXT
MS=ms71454350
ZOOM_verify_QSjXtfOfRHiY0O9gD5E4Ug
SPF v=spf1 include:mailer.duckduckgo.com include:spf.protection.outlook.com include:...
OSSRH-87525
bw=IOlfo6xQJX+xewM7+IiPqOSIPtLXKrWoS2RXCTPMmQZc
stripe-verification=e508f445dbb94b1ae51f7b48901897714b661f5298da43bb66b224973c82...
apple-domain-verification=XeKEoqnRNUfkUc5l
openai-domain-verification=dv-OKbsaUeVbNte6OPtWDpdt4Xr
cursor-domain-verification-nxwg1m=QRyFwelq3dM8RzBmvRla2boHy
anthropic-domain-verification-c7d48c=mGBhXlQHsvOc64IFwZsaKKVoQ
mistral-domain-verification=1b914b8749d84fc51987d1cd2b9f86b38617aa4d
CAALookup not available with standard resolver
Resolved in 42 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 184 ms total
PASS
1 redirect(s), 184 ms total
Info::
Single redirect
Got: https://www.duckduckgo.com → https://duckduckgo.com/ (301)
Info::
WWW normalization redirect

https://www.duckduckgo.com

30 ms · HTTP/1.1

301

https://duckduckgo.com/

154 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.duckduckgo.com30130 msHTTP/1.1nginx
2https://duckduckgo.com/200154 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 26 URLs
PASS
robots.txt present, sitemap with 26 URLs
Info::
robots.txt is present
Got: 382 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 26 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 382 B Sitemaps referenced 1 User-agents *, ia_archiver Blocking No — crawling allowed
User-agent: *
Disallow: /lite
Disallow: /html

# No search result pages
Disallow: /*?

# chrome new tab page
Disallow: /chrome_newtab

# Email Protection
Disallow: /email/
Allow: /email/$
Allow: /email/privacy-guarantees
Allow: /email/privacy-terms

# Old Privacy page
Disallow: /2012-privacy-policy

User-agent: ia_archiver
Disallow: /

Sitemap: https://duckduckgo.com/sitemap.xml

A
Domain Intelligence
duckduckgo.com — via NameCheap, Inc., 18 years, 8 months old, hosted on Microsoft Azure
PASS
duckduckgo.com — via NameCheap, Inc., 18 years, 8 months old, hosted on Microsoft Azure
Warning::
Domain expires in 71 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 23, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: NameCheap, Inc.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

EXPIRED

June 23, 2026

SSL certificate

252 days

Issued by DigiCert Inc

Domain age

18 years, 8 months

Registered November 11, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

52.149.246.39

Registrar

NameCheap, Inc.

Lock status unknown 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar NameCheap, Inc.
Created November 11, 2007 (18 years, 8 months ago)
Expires June 23, 2026 (2 months)
Last Updated May 24, 2025
Name Servers dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns01.quack-dns.com, ns02.quack-dns.com, ns03.quack-dns.com, ns04.quack-dns.com
DNSSEC Not enabled
Hosting
IP Address 52.149.246.39
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

A+
HTTP Probe Timing
Total 48 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
23 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
8 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
49 ms
Total Time Total request time from DNS lookup through full response.
49 ms

Connection waterfall

DNS Lookup 23 ms TCP Connect 8 ms TLS Handshake 11 ms Server Processing 8 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback