Skip to content
https://rediff.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Santa Clara, United States
302 Found
Checks
9
4 PASS 3 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2600:1406:3a00:33::170b:cff2, 2600:1406:3a00:33::170b:cff3
Info::
IPv6 connection error
Got: dial tcp6 [2600:1406:3a00:33::170b:cff2]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2600:1406:3a00:33::170b:cff2, 2600:1406:3a00:33::170b:cff3 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.rediff.com/
200https://rediff.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://rediff.com/ → http://www.rediff.com/

HTTP version does not redirect to HTTPS

B
Redirect Chain
2 redirect(s), 106 ms total
REVIEW
2 redirect(s), 106 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://rediff.com to https://www.rediff.com/
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://rediff.com

https://rediff.com

60 ms · HTTP/1.0

302

http://www.rediff.com/

21 ms · HTTP/1.1

301

https://www.rediff.com/

26 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rediff.com30260 msHTTP/1.0AkamaiGHost
2http://www.rediff.com/30121 msHTTP/1.1AkamaiGHost
3https://www.rediff.com/20026 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://rediff.com to https://www.rediff.com/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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

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

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
2 A records, 10 ms lookup
PASS
2 A records, 10 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.212.62.205, 23.212.62.206
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1406:3a00:33::170b:cff2, 2600:1406:3a00:33::170b:cff3
Info::
8 nameserver(s) configured
Got: use4.akam.net, ns1-245.akam.net, eur4.akam.net, use9.akam.net, usc2.akam.net, asia2.akam.net, eur1.akam.net, ns1-225.akam.net
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: 10 ms
Got: 10 ms
A23.212.62.205, 23.212.62.206
AAAA2600:1406:3a00:33::170b:cff2, 2600:1406:3a00:33::170b:cff3
CNAME—
NSuse4.akam.net, ns1-245.akam.net, eur4.akam.net, use9.akam.net, usc2.akam.net, asia2.akam.net, eur1.akam.net, ns1-225.akam.net
MX
10 mx.rediffmail.rediff.akadns.net
TXT
_v0dumjhw7ngs6dbf02a6czrz7a8dn64
SPF v=spf1 ip4:119.252.144.0/20 ip4:202.137.232.0/21 ip4:114.31.224.0/20 ip4:119.252...
_5rftjhqrd9h572ksplr01dlz87j3n15
google-site-verification=kqEbUAc_AScWut-4eJZyD5tAX9yR9mo1sRoZdOS0LPc
s6h03v7l4jqwclphd8h31wtbqf98mfd4
CAALookup not available with standard resolver
Resolved in 10 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+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 608 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
Sitemap index with 9 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 608 B Sitemaps referenced 9 User-agents * Blocking No — crawling allowed
# http://www.rediff.com: robots.txt
#
Sitemap: https://www.rediff.com/sitemap.xml
Sitemap: https://www.rediff.com/gnewssitemap.xml
Sitemap: https://www.rediff.com/daily-sitemap.xml
Sitemap: https://www.rediff.com/newssitemap.xml
Sitemap: https://www.rediff.com/moviessitemap.xml
Sitemap: https://www.rediff.com/sportssitemap.xml
Sitemap: https://www.rediff.com/businesssitemap.xml
Sitemap: https://www.rediff.com/getaheadsitemap.xml 
Sitemap: https://www.rediff.com/cricketsitemap.xml

User-agent: *
Disallow: /uim/
Disallow: /images/
Disallow: /messageboard/
Disallow: /newsletters/
Disallow: /cms/print.jsp
sitemap.xml 200 OK
Type Sitemap Index URLs 9 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
rediff.com — via Network Solutions, LLC, 29 years, 7 months old, hosted on Akamai
PASS
rediff.com — via Network Solutions, LLC, 29 years, 7 months old, hosted on Akamai
Info::
Domain registered until Feb 9, 2034 (7 years, 11 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: Network Solutions, LLC
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: Akamai
Got: AS20940
Domain expiry

2795 days

February 9, 2034

SSL certificate

213 days

Issued by DigiCert Inc

Domain age

29 years, 7 months

Registered February 8, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

23.212.62.206

Registrar

Network Solutions, LLC

Unlocked 8 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 Network Solutions, LLC
Created February 8, 1997 (29 years, 7 months ago)
Expires February 9, 2034 (7 years, 11 months)
Last Updated January 3, 2025
Name Servers asia2.akam.net, eur1.akam.net, eur4.akam.net, ns1-225.akam.net, ns1-245.akam.net, usc2.akam.net, use4.akam.net, use9.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.212.62.206
ASN AS20940 (AKAMAI-ASN1, NL)
Provider Akamai
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

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

Connection waterfall

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