Skip to content
https://electrek.co

Infrastructure

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

Connection waterfall

DNS Lookup 26 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 790 ms Content Transfer 8 ms
B
TLS Certificate Expiry & Recommendations
76 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

76
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, 33 ms lookup
PASS
1 A records, 33 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: ns1.wordpress.com, ns2.wordpress.com, ns3.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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 33 ms
Got: 33 ms
A192.0.66.2
AAAA—
CNAME—
NSns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
TXT
google-site-verification=_pYSKm4aY7R9pNQNSeMWBy4YN1zkYWp2EgXUrtLXfmg
facebook-domain-verification=wo23egd1lytt5myymt79k2n4rbghmg
CAALookup not available with standard resolver
Resolved in 33 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.

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

https://electrek.co

704 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://electrek.co200704 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 49 URLs
PASS
robots.txt present, sitemap with 49 URLs
Info::
robots.txt is present
Got: 778 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 49 entries
Info::
Sitemap index with 49 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 778 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/3/wpforms/
# ---------------------------
# END WPFORMS BLOCK
# Sitemap archive
Sitemap: https://electrek.co/sitemap.xml


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

Sitemap: https://electrek.co/sitemap_index.xml
Sitemap: https://925.co/sitemap_index.xml
Sitemap: https://dronedj.com/sitemap_index.xml
Sitemap: https://9to5google.com/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 49 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.electrek.co/
200https://electrek.co/

Preferred variant: non-www

HTTP → HTTPS

301http://electrek.co/ → https://electrek.co/

Consistent

A+
Domain Intelligence
electrek.co — via Tucows Domains Inc., 12 years, 8 months old, hosted on WordPress.com (Automattic)
PASS
electrek.co — via Tucows Domains Inc., 12 years, 8 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Sep 26, 2026 (5 months remaining)
Info::
Registrar: Tucows Domains Inc.
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

103 days

September 26, 2026

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

12 years, 8 months

Registered September 27, 2013

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.2

Registrar

Tucows Domains Inc.

Locked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Tucows Domains Inc.
Created September 27, 2013 (12 years, 8 months ago)
Expires September 26, 2026 (5 months)
Last Updated August 31, 2025
Name Servers ns1.wordpress.com, ns3.wordpress.com, ns2.wordpress.com
Hosting
IP Address 192.0.66.2
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: whois (1.5s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — 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