Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BHTTP Probe TimingTotal 827 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations76 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
ADNS Records1 A records, 33 ms lookupPASS
| A | 192.0.66.2 |
| AAAA | — |
| CNAME | — |
| NS | ns1.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 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
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'.
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 ChainNo redirects — direct accessPASS
https://electrek.co
704 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://electrek.co | 200 | 704 ms | HTTP/1.1 | nginx |
A+Crawlabilityrobots.txt present, sitemap with 49 URLsPASS
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
- https://electrek.co/post-sitemap.xml
- https://electrek.co/post-sitemap2.xml
- https://electrek.co/post-sitemap3.xml
- https://electrek.co/post-sitemap4.xml
- https://electrek.co/post-sitemap5.xml
- https://electrek.co/post-sitemap6.xml
- https://electrek.co/post-sitemap7.xml
- https://electrek.co/post-sitemap8.xml
- https://electrek.co/post-sitemap9.xml
- https://electrek.co/post-sitemap10.xml
- https://electrek.co/post-sitemap11.xml
- https://electrek.co/post-sitemap12.xml
- https://electrek.co/post-sitemap13.xml
- https://electrek.co/post-sitemap14.xml
- https://electrek.co/post-sitemap15.xml
- https://electrek.co/post-sitemap16.xml
- https://electrek.co/post-sitemap17.xml
- https://electrek.co/post-sitemap18.xml
- https://electrek.co/post-sitemap19.xml
- https://electrek.co/post-sitemap20.xml
- https://electrek.co/post-sitemap21.xml
- https://electrek.co/post-sitemap22.xml
- https://electrek.co/post-sitemap23.xml
- https://electrek.co/post-sitemap24.xml
- https://electrek.co/post-sitemap25.xml
- https://electrek.co/post-sitemap26.xml
- https://electrek.co/post-sitemap27.xml
- https://electrek.co/post-sitemap28.xml
- https://electrek.co/post-sitemap29.xml
- https://electrek.co/post-sitemap30.xml
- https://electrek.co/post-sitemap31.xml
- https://electrek.co/post-sitemap32.xml
- https://electrek.co/post-sitemap33.xml
- https://electrek.co/post-sitemap34.xml
- https://electrek.co/post-sitemap35.xml
- https://electrek.co/post-sitemap36.xml
- https://electrek.co/post-sitemap37.xml
- https://electrek.co/page-sitemap.xml
- https://electrek.co/ninetofive_section-s...
- https://electrek.co/web-story-sitemap.xm...
- https://electrek.co/ninetofive_podcasts-...
- https://electrek.co/ninetofive_guides-si...
- https://electrek.co/ninetofive_guides-si...
- https://electrek.co/ninetofive_guides-si...
- https://electrek.co/ninetofive_guides-si...
- https://electrek.co/ninetofive_guides-si...
- https://electrek.co/ninetofive_guides-si...
- https://electrek.co/author-sitemap.xml
- https://electrek.co/news-sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceelectrek.co — via Tucows Domains Inc., 12 years, 8 months old, hosted on WordPress.com (Automattic)PASS
48 days
September 26, 2026
76 days
Issued by Let's Encrypt
12 years, 8 months
Registered September 27, 2013
Status unknown
Protects against DNS spoofing
WordPress.com (Automattic)
ASN AS2635
192.0.66.2
Tucows Domains Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice