Skip to content
https://channel4.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
301 Moved Permanently
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.

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
156 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
2 A records, 8 ms lookup
PASS
2 A records, 8 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.211.175.112, 46.51.152.173
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1312.awsdns-36.org, ns-1975.awsdns-54.co.uk, ns-216.awsdns-27.com, ns-614.awsdns-12.net
Info::
2 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: 8 ms
Got: 8 ms
A52.211.175.112, 46.51.152.173
AAAA
CNAME
NSns-1312.awsdns-36.org, ns-1975.awsdns-54.co.uk, ns-216.awsdns-27.com, ns-614.awsdns-12.net
MX
10 eu-smtp-inbound-2.mimecast.com
10 eu-smtp-inbound-1.mimecast.com
TXT
MS=ms29366648
ZOOM_verify_Y2dFAf9XSvKUg2ORTS2gbA
_d9fobryb9tqfk45536hpew2uv4vk7fj
_fll40i3jwu0v9mdj8by1zeexxqnwn49
facebook-domain-verification=aoj6xe4ia6zv9pa60oyg0gb8b09qn9
google-site-verification=74fv47FmtsFTQKexq3E3Aoc9wzfloilWotg0sGO9zHM
jg02l4gtljwdvp587l9yst7wfhy49w91
q348mw8dy8f5625sp3b8mcdjh7gq1smh
SPF v=spf1 ip4:52.16.14.52 ip4:195.140.184.0/22 ip4:91.192.40.0/22 include:amazonses...
CAALookup not available with standard resolver
Resolved in 8 ms

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), 453 ms total
PASS
1 redirect(s), 453 ms total
Info::
Single redirect
Got: https://channel4.com → https://www.channel4.com/ (301)
Info::
WWW normalization redirect

https://channel4.com

331 ms · HTTP/1.1

301

https://www.channel4.com/

122 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://channel4.com301331 msHTTP/1.1nginx
2https://www.channel4.com/200122 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1001 URLs
PASS
robots.txt present, sitemap with 1001 URLs
Info::
robots.txt is present
Got: 1044 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1001 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1044 B Sitemaps referenced 2 User-agents Claude-Web, Bytespider, PetalBot, omgili, Google-CloudVertexBot, AdsBot-Google, ChatGPT-User, anthropic-ai, cohere-ai, meta-externalagent, Googlebot, Google-Extended, OAI-SearchBot, YandexAdditional, YandexAdditionalBot, TurnitinBot, *, CCBot, ClaudeBot, Applebot-Extended, GPTBot, PerplexityBot Blocking No — crawling allowed
Crawl-delay: 5
Sitemap: https://www.channel4.com/news/sitemap.xml

Sitemap: https://www.channel4.com/sitemap.xml


User-agent: TurnitinBot

Disallow: /


User-agent: *
Disallow: /news/?*
Disallow: /news/*/?*

Disallow: /press/unregistered-image-search?*
Disallow: /press/content-search?*

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-Agent: omgili
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: Google-Extended
Disallow: /

User-Agent: PerplexityBot
Disallow: /

User-agent: Google-CloudVertexBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: YandexAdditional
Disallow: /

User-agent: YandexAdditionalBot
Disallow: /

User-agent: AdsBot-Google
Allow: /

User-agent: Googlebot
Allow: /
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.channel4.com/
200https://channel4.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
channel4.com — via CSC Corporate Domains, Inc., 30 years, 10 months old, hosted on AWS
PASS
channel4.com — via CSC Corporate Domains, Inc., 30 years, 10 months old, hosted on AWS
Info::
Domain registered until Nov 16, 2026 (6 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: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

122 days

November 16, 2026

SSL certificate

156 days

Issued by Sectigo Limited

Domain age

30 years, 10 months

Registered November 17, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.211.175.112

Registrar

CSC Corporate Domains, Inc.

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created November 17, 1995 (30 years, 10 months ago)
Expires November 16, 2026 (6 months)
Last Updated November 12, 2025
Name Servers ns-1312.awsdns-36.org, ns-1975.awsdns-54.co.uk, ns-216.awsdns-27.com, ns-614.awsdns-12.net
DNSSEC Not enabled
Hosting
IP Address 52.211.175.112
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 6 ms TCP Connect 80 ms TLS Handshake 163 ms Server Processing 81 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