Skip to content
https://www.aljazeera.net

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 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, 34 ms lookup
REVIEW
1 A records, 34 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 2.22.209.66
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:e0:890::2392, 2a02:26f0:e0:8af::2392
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: www.aljazeera.net.edgekey.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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: 34 ms
Got: 34 ms
A2.22.209.66
AAAA2a02:26f0:e0:890::2392, 2a02:26f0:e0:8af::2392
CNAMEwww.aljazeera.net.edgekey.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 34 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

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
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/3 IPs match cert SAN
REVIEW
0/3 IPs match cert SAN
Info::
PTR for 2.22.209.66 does not match any cert SAN: a2-22-209-66.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a02:26f0:e0:890::2392 does not match any cert SAN: g2a02-26f0-00e0-0890-0000-0000-0000-2392.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a02:26f0:e0:8af::2392 does not match any cert SAN: g2a02-26f0-00e0-08af-0000-0000-0000-2392.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
TLS Certificate Expiry & Recommendations
184 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 26ms across 3 resolvers (spread 15ms)
PASS
Mean 26ms across 3 resolvers (spread 15ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 30ms
Got: 30ms via 8.8.8.8:53
Info::
Quad9: 32ms
Got: 32ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.aljazeera.net

https://www.aljazeera.net

18 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.aljazeera.net20018 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:e0:890::2392, 2a02:26f0:e0:8af::2392
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:e0:890::2392, 2a02:26f0:e0:8af::2392 Connection Reachable (0 ms)
A+
Crawlability
robots.txt present, sitemap with 343 URLs
PASS
robots.txt present, sitemap with 343 URLs
Info::
robots.txt is present
Got: 1588 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 343 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1588 B Sitemaps referenced 5 User-agents GPTBot, Bytespider, *, ClaudeBot, cohere-ai, PerplexityBot, AmazonAdBot, anthropic-ai, ChatGPT-User, Claude-Web Blocking No — crawling allowed
# Al Jazeera Media Network content is made available for your personal, non-commercial 
# use subject to our Terms and Conditions: 
# https://www.aljazeera.com/terms-and-conditions/
# Any other uses are not permitted, including but not limited to:
# (1) the development of any software, machine learning, artificial intelligence (AI),
# and/or large language models (LLMs); 
# (2) text and data mining activities;
# (3) creating or providing archived or cached data sets containing our content to others; and/or
# (4) any commercial purposes.
# Use of any device, tool, or process designed to data mine or scrape the content
# using automated means is prohibited without prior written permission from 
# Al Jazeera Media Network. Contact https://network.aljazeera.net/en/contact for assistance.

User-agent: *
Disallow: /api
Disallow: /asset-manifest.json
Allow: /search/$
Disallow: /search/
Disallow: /home/search?q=

# Allow Rules

User-agent: AmazonAdBot
Allow: /

# Disallow Rules

User-agent: anthropic-ai
Disallow: / 

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: / 

User-agent: Claude-Web
Disallow: /

User-agent: cohere-ai
Disallow: / 

User-agent: GPTBot
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Bytespider
Disallow: /


# Sitemaps

Sitemap: https://www.aljazeera.net/news-sitemap.xml 
Sitemap: https://www.aljazeera.net/sitemaps/article-archive.xml
Sitemap: https://www.aljazeera.net/sitemaps/article-new.xml
Sitemap: https://www.aljazeera.net/sitemaps/video-archive.xml
Sitemap: https://www.aljazeera.net/sitemaps/video-new.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.aljazeera.net/
301https://aljazeera.net/

Preferred variant: www

HTTP → HTTPS

301http://www.aljazeera.net/ https://www.aljazeera.net/

Consistent

A+
Domain Intelligence
aljazeera.net — via MarkMonitor Inc., 30 years, 1 months old, hosted on AWS
PASS
aljazeera.net — via MarkMonitor Inc., 30 years, 1 months old, hosted on AWS
Info::
Domain registered until Aug 29, 2029 (3 years, 4 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: MarkMonitor 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

1199 days

August 29, 2029

SSL certificate

184 days

Issued by DigiCert Inc

Domain age

30 years, 1 months

Registered August 30, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.59.77.182

Registrar

MarkMonitor 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 MarkMonitor Inc.
Created August 30, 1996 (30 years, 1 months ago)
Expires August 29, 2029 (3 years, 4 months)
Last Updated October 18, 2023
Name Servers ns-1302.awsdns-34.org, ns-1814.awsdns-34.co.uk, ns-321.awsdns-40.com, ns-744.awsdns-29.net
DNSSEC Not enabled
Hosting
IP Address 13.59.77.182
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 54 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
50 ms
Total Time Total request time from DNS lookup through full response.
54 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 0 ms TLS Handshake 4 ms Server Processing 13 ms Content Transfer 4 ms
A+
Health Check Endpoint
Health endpoint at https://www.aljazeera.net/health (HTTP 200)
PASS
Health endpoint at https://www.aljazeera.net/health (HTTP 200)
Info::
Public health endpoint at https://www.aljazeera.net/health
Got: https://www.aljazeera.net/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback