Skip to content
https://timesnownews.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
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
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 403 Expected: 301 redirect to HTTPS

www / non-www

200https://www.timesnownews.com/
200https://timesnownews.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

403http://timesnownews.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.196.3.136, 23.196.3.166
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:141b:9000::6846:7989, 2600:141b:9000::6846:79b8
Info::
6 nameserver(s) configured
Got: a13-66.akam.net, a7-65.akam.net, a28-67.akam.net, a10-65.akam.net, a18-65.akam.net, a1-84.akam.net
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: 9 ms
Got: 9 ms
A23.196.3.136, 23.196.3.166
AAAA2600:141b:9000::6846:7989, 2600:141b:9000::6846:79b8
CNAME
NSa13-66.akam.net, a7-65.akam.net, a28-67.akam.net, a10-65.akam.net, a18-65.akam.net, a1-84.akam.net
MX
TXT
google-site-verification=rHD62HSas3wxrARlc6-3ATchgnYuFEgwK0ms0VMs2JI
tollbit-domain-verification=d9cdbcd0d21d4d3f7bb50015db3c2c9b06ab02ef1fd5a39d9912...
google-site-verification=dWRHHGU6aQE-W0nUrzvKstuj_DFEMBteOLzuGwcFfEo
google-site-verification=jYtguPL1EXrF_Uwwv59x_4GzDfmSSeVcx6VacB4RlVM
facebook-domain-verification=32gf4hvskay4g2q080bd6kt750jnie
CAALookup not available with standard resolver
Resolved in 9 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.

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)

A
Redirect Chain
1 redirect(s), 269 ms total
PASS
1 redirect(s), 269 ms total
Info::
Single redirect
Got: https://timesnownews.com → https://www.timesnownews.com/ (301)
Info::
WWW normalization redirect

https://timesnownews.com

21 ms · HTTP/1.1

301

https://www.timesnownews.com/

248 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://timesnownews.com30121 msHTTP/1.1AkamaiGHost
2https://www.timesnownews.com/200248 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:141b:9000::6846:7989, 2600:141b:9000::6846:79b8
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:141b:9000::6846:7989, 2600:141b:9000::6846:79b8 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 430 URLs
PASS
robots.txt present, sitemap with 430 URLs
Info::
robots.txt is present
Got: 1050 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 430 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1050 B Sitemaps referenced 1 User-agents Yandex, BLEXBot, AmazonAdBot, OAI-SearchBot, Screaming Frog SEO Spider, Meta-ExternalAgent, Applebot, ClaudeBot, ChatGPT-User, SemrushBot, Amazonbot, DotBot, Bytespider, *, PetalBot, AdsBot-Google, Baiduspider Blocking No — crawling allowed
User-agent: GPTBot
Allow: /


User-agent: ChatGPT-User

Allow: /


User-agent: OAI-SearchBot

Allow: /


User-agent: *

Allow: /

Disallow: /wapi/

Disallow: /presite

Disallow: /story/*

Disallow: /test-section/

Disallow: /embed/

Disallow: /search-result/


#Sitemaps

Sitemap: https://www.timesnownews.com/google-news-sitemap-en.xml


#Baiduspider

User-agent: Baiduspider

Disallow: /


#Yandex

User-agent: Yandex

Disallow: /


User-agent: Screaming Frog SEO Spider

Disallow: /

 
User-agent: SemrushBot

Disallow: /


User-agent: Meta-ExternalAgent

Disallow: /


User-agent: Applebot

Disallow: /


# Block Amazon's bot

User-agent: Amazonbot

Disallow: /


# Block BLEXBot

User-agent: BLEXBot

Disallow: /


# Block Huawei's PetalBot

User-agent: PetalBot

Disallow: /


# Block Moz's DotBot

User-agent: DotBot

Disallow: /


User-agent: Bytespider

Disallow: /


# Block Anthropic's ClaudeBot

User-agent: ClaudeBot

Disallow: /


User-agent: AdsBot-Google

Disallow: /[0-9]*$


User-agent: AmazonAdBot

Allow: /


A
Domain Intelligence
timesnownews.com — via GoDaddy.com, LLC, 18 years old
PASS
timesnownews.com — via GoDaddy.com, LLC, 18 years old
Warning::
Domain expires in 69 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 1, 2026
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
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.
Domain expiry

15 days

July 1, 2026

SSL certificate

183 days

Issued by DigiCert Inc

Domain age

18 years

Registered July 1, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:141b:1c00:1d::172c:cb0d

Registrar

GoDaddy.com, LLC

Unlocked 6 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created July 1, 2008 (18 years ago)
Expires July 1, 2026 (2 months)
Last Updated January 10, 2026
Name Servers a1-84.akam.net, a10-65.akam.net, a13-66.akam.net, a18-65.akam.net, a28-67.akam.net, a7-65.akam.net
DNSSEC Not enabled
Hosting
IP Address 2600:141b:1c00:1d::172c:cb0d
Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 23 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.
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.
23 ms
Total Time Total request time from DNS lookup through full response.
24 ms

Connection waterfall

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