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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
302 Found
Checks
9
6 PASS 2 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.

B
DNS Records
1 A records, 137 ms lookup
REVIEW
1 A records, 137 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 151.101.93.111
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a04:4e42:16::367
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: dualstack.guardian.map.fastly.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 137 ms
Got: 137 ms
A151.101.93.111
AAAA2a04:4e42:16::367
CNAMEdualstack.guardian.map.fastly.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 137 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
Redirect Chain
1 redirect(s), 49 ms total
PASS
1 redirect(s), 49 ms total
Info::
Single redirect
Got: https://www.theguardian.com → https://www.theguardian.com/international (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.theguardian.com

https://www.theguardian.com

13 ms · HTTP/1.1

302

https://www.theguardian.com/internationa...

36 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.theguardian.com30213 msHTTP/1.1
2https://www.theguardian.com/internationa...20036 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a04:4e42:16::367
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a04:4e42:16::367 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 416 URLs
PASS
robots.txt present, sitemap with 416 URLs
Info::
robots.txt is present
Got: 2794 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 416 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2794 B Sitemaps referenced 2 User-agents *, Mojeek, ClaudeBot, Amzn-SearchBot, CCBot, MoodleBot, SeznamBot, Claude-SearchBot, ImageSift, Applebot-Extended, YandexAdditionalBot, NewsNow, PetalBot, coccocbot-web, meta-externalagent, DuckAssistBot, Google-CloudVertexBot, Bytespider, anthropic-ai, YandexAdditional, TurnitinBot, scalepostAI, Mediapartners-Google, FacebookBot, Seekr, AwarioRssBot, AwarioSmartBot, JenkersBot, Arquivo-web-crawler, PerplexityBot, yacy, Claude-User, SentiOne, Buck, Amazonbot, YouBot Blocking No — crawling allowed
# This is the robots.txt file for theguardian.com

# Guardian content is made available under our terms and conditions of use.
# Any other uses are not permitted, incl. but not limited to: for large language
# models (LLMs), machine learning and/or artificial intelligence-related
# purposes; with any of the aforementioned technologies; and/or for any
# commercial purposes. Contact licensing@theguardian.com for assistance

User-agent: *
Disallow: /sendarticle/
Disallow: /Users/
Disallow: /users/
Disallow: /*/print$
Disallow: /email/
Disallow: /contactus/
Disallow: /share/
Disallow: /websearch
Disallow: /*?commentpage=
Disallow: /whsmiths/
Disallow: /external/overture/
Disallow: /discussion/report-abuse/*
Disallow: /discussion/report-abuse-ajax/*
Disallow: /discussion/comment-permalink/*
Disallow: /discussion/report-abuse/*
Disallow: /discussion/user-report-abuse/*
Disallow: /discussion/handlers/*
Disallow: /discussion/your-profile
Disallow: /discussion/your-comments
Disallow: /discussion/edit-profile
Disallow: /discussion/search/comments
Disallow: /discussion/*
Disallow: /search
Disallow: /music/artist/*
Disallow: /music/album/*
Disallow: /books/data/*
Disallow: /settings/
Disallow: /embed/
Disallow: /*styles/js-on.css$
Disallow: /sport/olympics/2008/events/*
Disallow: /sport/olympics/2008/medals/*
Disallow: /f/healthcheck
Disallow: /sections
Disallow: /top-stories
Disallow: /most-read/sport
Disallow: /articles
Disallow: /global$
Disallow: /*/feedarticle/*
Disallow: /travel/2013/aug/22/been-there-readers-competition?*
Disallow: /preference/*
Disallow: /59666047/
Disallow: /print/
Disallow: /info/tech-feedback
Disallow: /production-monitoring/
Disallow: *.emailjson
Disallow: *.emailtxt
Disallow: /headline.txt
Disallow: *?*dcr=apps*

User-agent: Mediapartners-Google
Disallow:

Sitemap: http://www.theguardian.com/sitemaps/news.xml
Sitemap: http://www.theguardian.com/sitemaps/video.xml

User-agent: NewsNow
User-agent: CCBot
User-agent: TurnitinBot
User-agent: PetalBot
User-agent: MoodleBot
User-agent: FacebookBot
User-agent: Bytespider
User-agent: Mojeek
User-agent: JenkersBot
User-agent: Seekr
User-agent: YouBot
User-agent: Arquivo-web-crawler
User-agent: coccocbot-web
User-agent: SeznamBot
User-Agent: PerplexityBot
User-Agent: yacy
User-agent: anthropic-ai
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: SentiOne
User-agent: ImageSift
User-agent: Applebot-Extended
User-agent: YandexAdditional
User-agent: YandexAdditionalBot
User-agent: scalepostAI
User-agent: Buck
User-agent: meta-externalagent
User-agent: Amazonbot
User-agent: DuckAssistBot
User-agent: Google-CloudVertexBot
User-agent: Amzn-SearchBot
Disallow: /

License: https://theguardian.com/license.xml

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.theguardian.com/
301https://theguardian.com/

Preferred variant: www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
theguardian.com — via GoDaddy.com, LLC, 32 years, 2 months old
PASS
theguardian.com — via GoDaddy.com, LLC, 32 years, 2 months old
Info::
Domain registered until Jul 5, 2026 (3 months remaining)
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: GoDaddy.com, LLC
Domain expiry

19 days

July 5, 2026

SSL certificate

217 days

Issued by GlobalSign nv-sa

Domain age

32 years, 2 months

Registered July 6, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:4e42::367

Registrar

GoDaddy.com, LLC

Lock status unknown 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar GoDaddy.com, LLC
Created July 6, 1994 (32 years, 2 months ago)
Expires July 5, 2026 (3 months)
Last Updated July 5, 2025
Name Servers dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns01.theguardiandns.com, ns02.theguardiandns.com, ns03.theguardiandns.com, ns04.theguardiandns.com
DNSSEC Not enabled
Hosting
IP Address 2a04:4e42::367
Data source: rdap (0.8s)

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 14 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
14 ms
Total Time Total request time from DNS lookup through full response.
14 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 2 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