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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 REVIEW
B
DNS Records
4 A records, 26 ms lookup
REVIEW
4 A records, 26 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.1.91, 151.101.193.91, 151.101.65.91, 151.101.129.91
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: n.sni.global.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: 26 ms
Got: 26 ms
A151.101.1.91, 151.101.193.91, 151.101.65.91, 151.101.129.91
AAAA
CNAMEn.sni.global.fastly.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 26 ms

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)

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
TLS Certificate Expiry & Recommendations
109 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.theverge.com

https://www.theverge.com

8 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.theverge.com2008 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 33 URLs
PASS
robots.txt present, sitemap with 33 URLs
Info::
robots.txt is present
Got: 1855 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 33 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1855 B Sitemaps referenced 2 User-agents Google-Extended, Applebot, CCBot, ClaudeBot, Diffbot, Omgilibot, Googlebot-News, Applebot-Extended, ChatGPT-User, Claude-Web, FacebookBot, Omgili, *, GPTBot, anthropic-ai, Bytespider, ImagesiftBot, PerplexityBot, YouBot Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

User-agent: GPTBot
Allow: /

User-agent: Google-Extended
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Applebot
Allow: /

User-agent: anthropic-ai
Allow: /ad/827622/how-renault-groups-vehicle-development-merges-real-life-with-virtual-reality
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Allow: /ad/827622/how-renault-groups-vehicle-development-merges-real-life-with-virtual-reality
Disallow: /

User-agent: ChatGPT-User
Allow: /ad/827622/how-renault-groups-vehicle-development-merges-real-life-with-virtual-reality
Disallow: /

User-agent: ClaudeBot
Allow: /ad/827622/how-renault-groups-vehicle-development-merges-real-life-with-virtual-reality
Disallow: /

User-agent: Claude-Web
Allow: /ad/827622/how-renault-groups-vehicle-development-merges-real-life-with-virtual-reality
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: ImagesiftBot
Disallow: /

User-agent: Omgilibot
Disallow: /

User-agent: Omgili
Disallow: /

User-agent: PerplexityBot
Allow: /ad/827622/how-renault-groups-vehicle-development-merges-real-life-with-virtual-reality
Disallow: /

User-agent: YouBot
Disallow: /

User-agent: Googlebot-News
Disallow: /ad
Disallow: /sponsored

User-agent: *
Allow: /ad/827622/how-renault-groups-vehicle-development-merges-real-life-with-virtual-reality
Disallow: /admin
Disallow: /newfanshot
Disallow: /users/*/replies
Disallow: /users/*/comments
Disallow: /login
Disallow: /account
Disallow: /auth/*
Disallow: /chorus_auth
Disallow: /sso
Disallow: /search
Disallow: /the-highlight$

User-agent: *
Disallow: /share$
Disallow: /share/*
Disallow: /share?*

# Google news sitemap
Sitemap: https://www.theverge.com/sitemaps/google_news

# Sitemap archive
Sitemap: https://www.theverge.com/sitemaps

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.theverge.com/
301https://theverge.com/

Preferred variant: www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
theverge.com — via Amazon Registrar, Inc., 27 years, 9 months old, hosted on Fastly
PASS
theverge.com — via Amazon Registrar, Inc., 27 years, 9 months old, hosted on Fastly
Info::
Domain registered until Nov 10, 2026 (7 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: Amazon Registrar, Inc.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

121 days

November 10, 2026

SSL certificate

109 days

Issued by GlobalSign nv-sa

Domain age

27 years, 9 months

Registered November 11, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.193.91

Registrar

Amazon Registrar, Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Amazon Registrar, Inc.
Created November 11, 1998 (27 years, 9 months ago)
Expires November 10, 2026 (7 months)
Last Updated October 6, 2025
Name Servers ns-11.awsdns-01.com, ns-1312.awsdns-36.org, ns-1883.awsdns-43.co.uk, ns-637.awsdns-15.net
DNSSEC Not enabled
Hosting
IP Address 151.101.193.91
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 78 ms TCP Connect 0 ms TLS Handshake 2 ms Server Processing 2 ms Content Transfer 3 ms
A+
CDN & Delivery
Fastly (HIT, HIT)
PASS
Fastly (HIT, HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-iad-kiad7000122-IAD, cache-toj-leto2350032-TOJ
Info::
CDN cache status: HIT, HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT, HIT Evidence x-served-by: cache-iad-kiad7000122-IAD, cache-toj-leto2350032-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback