Skip to content
https://eweek.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.eweek.com/
200https://eweek.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://eweek.com/ → https://eweek.com/

Consistent

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

Certificate validity

88
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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f07869c6a1cd784-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f07869c6a1cd784-CDG
A+
DNS Records
3 A records, 35 ms lookup
PASS
3 A records, 35 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.6.137, 104.26.7.137, 172.67.68.158
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:449e, 2606:4700:20::681a:789, 2606:4700:20::681a:689
Info::
2 nameserver(s) configured
Got: edna.ns.cloudflare.com, will.ns.cloudflare.com
Info::
5 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: 35 ms
Got: 35 ms
A104.26.6.137, 104.26.7.137, 172.67.68.158
AAAA2606:4700:20::ac43:449e, 2606:4700:20::681a:789, 2606:4700:20::681a:689
CNAME—
NSedna.ns.cloudflare.com, will.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=8HN7_qH7PTo1NOoxTHSZ7zQX4VvYoGP-Xc_Ps_79SJI
google-site-verification=XztZ-H8fDlGogcP40xVcjM0O-PGSVOL7BG5KaI2W-Cg
SPF v=spf1 include:spf.mailjet.com include:amazonses.com include:_spf.google.com inc...
google-site-verification=51k8vwphzd400o_y3o-vM1ChO__K5-WqdwBVR8oG2LI
google-site-verification=wHG3oVRhlb2cZoOYwJfmeJqS_PIoDQBG6jd-E0o0FUs
CAALookup not available with standard resolver
Resolved in 35 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), 310 ms total
PASS
1 redirect(s), 310 ms total
Info::
Single redirect
Got: https://eweek.com → https://www.eweek.com/ (301)
Info::
WWW normalization redirect

https://eweek.com

58 ms · HTTP/1.1

301

https://www.eweek.com/

252 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://eweek.com30158 msHTTP/1.1cloudflare
2https://www.eweek.com/200252 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::ac43:449e, 2606:4700:20::681a:789, 2606:4700:20::681a:689
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::ac43:449e, 2606:4700:20::681a:789, 2606:4700:20::681a:689 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 227 URLs
PASS
robots.txt present, sitemap with 227 URLs
Info::
robots.txt is present
Got: 560 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 227 entries
Info::
Sitemap index with 227 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 560 B Sitemaps referenced 1 User-agents *, SemrushBot, SemrushBot-BA, SemrushBot-SA, SemrushBot-SI, SemrushBot-SWA, SemrushBot-CT, SemrushBot-BM, SemrushBot-SEOAB Blocking No — crawling allowed
User-agent: *
Disallow: /wp/wp-admin/
Allow: /wp/wp-admin/admin-ajax.php


User-agent: SemrushBot
Disallow: /

User-agent: SemrushBot-SA
Disallow: /

User-agent: SemrushBot-BA
Disallow: /

User-agent: SemrushBot-SI
Disallow: /

User-agent: SemrushBot-SWA
Disallow: /

User-agent: SemrushBot-CT
Disallow: /

User-agent: SemrushBot-BM
Disallow: /

User-agent: SemrushBot-SEOAB
Disallow: /
	
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.eweek.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 227 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
eweek.com — via Name.com, Inc., 28 years, 3 months old
PASS
eweek.com — via Name.com, Inc., 28 years, 3 months old
Info::
Domain registered until Jul 26, 2026 (3 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: Name.com, 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.
Domain expiry

10 days

July 26, 2026

SSL certificate

88 days

Issued by Google Trust Services

Domain age

28 years, 3 months

Registered May 27, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:689

Registrar

Name.com, Inc.

Unlocked 2 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 Name.com, Inc.
Created May 27, 1998 (28 years, 3 months ago)
Expires July 26, 2026 (3 months)
Last Updated June 26, 2025
Name Servers edna.ns.cloudflare.com, will.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:689
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 107 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
50 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
108 ms
Total Time Total request time from DNS lookup through full response.
108 ms

Connection waterfall

DNS Lookup 50 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 19 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