Skip to content
https://9to5google.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
5 PASS 3 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
HTTP Probe Timing
Total 815 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
717 ms
Total Time Total request time from DNS lookup through full response.
815 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 710 ms Content Transfer 98 ms
B
TLS Certificate Expiry & Recommendations
40 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 3 ms lookup
PASS
1 A records, 3 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.wordpress.com, ns2.wordpress.com, ns1.wordpress.com
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: 3 ms
Got: 3 ms
A192.0.66.2
AAAA—
CNAME—
NSns3.wordpress.com, ns2.wordpress.com, ns1.wordpress.com
MX
10 mx1.forwardemail.net
10 mx2.forwardemail.net
TXT
ahrefs-site-verification_623a92e519b34da9418e97da2ede53be608a3d4b0e11d55cb6d9d59...
google-site-verification=Ft4_uGw_LE_TeFaEsIX2pKcNUlU19YV2t8s5kfjt78Y
forward-email-site-verification=X65R7W1KcW
SPF v=spf1 a mx include:spf.forwardemail.net include:_spf.google.com -all
facebook-domain-verification=uamvso5qe13g09bqq7r4iqddjiklig
CAALookup not available with standard resolver
Resolved in 3 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

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://9to5google.com

https://9to5google.com

8 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://9to5google.com2008 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 87 URLs
PASS
robots.txt present, sitemap with 87 URLs
Info::
robots.txt is present
Got: 781 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 87 entries
Info::
Sitemap index with 87 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 781 B Sitemaps referenced 9 User-agents Mediapartners-Google, * Blocking No — crawling allowed
User-agent: Mediapartners-Google
Disallow:
# START WPFORMS BLOCK
# ---------------------------
User-agent: *
Disallow: /wp-content/uploads/sites/4/wpforms/
# ---------------------------
# END WPFORMS BLOCK
# Sitemap archive
Sitemap: https://9to5google.com/sitemap.xml


# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://9to5google.com/sitemap_index.xml
Sitemap: https://925.co/sitemap_index.xml
Sitemap: https://dronedj.com/sitemap_index.xml
Sitemap: https://electrek.co/sitemap_index.xml
Sitemap: https://9to5toys.com/sitemap_index.xml
Sitemap: https://9to5mac.com/sitemap_index.xml
Sitemap: https://spaceexplored.com/sitemap_index.xml
Sitemap: https://connectthewatts.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 87 entries Valid XML Yes
Child Sitemaps:
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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.9to5google.com/
200https://9to5google.com/

Preferred variant: non-www

HTTP → HTTPS

301http://9to5google.com/ → https://9to5google.com/

Consistent

A+
Domain Intelligence
9to5google.com — via Tucows Domains Inc., 17 years, 5 months old, hosted on WordPress.com (Automattic)
PASS
9to5google.com — via Tucows Domains Inc., 17 years, 5 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Jan 29, 2027 (9 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: Tucows 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: WordPress.com (Automattic)
Got: AS2635
Domain expiry

228 days

January 29, 2027

SSL certificate

40 days

Issued by Let's Encrypt

Domain age

17 years, 5 months

Registered January 29, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.2

Registrar

Tucows Domains Inc.

Unlocked 3 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 Tucows Domains Inc.
Created January 29, 2009 (17 years, 5 months ago)
Expires January 29, 2027 (9 months)
Last Updated May 13, 2023
Name Servers ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
DNSSEC Not enabled
Hosting
IP Address 192.0.66.2
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (1.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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback