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 1111 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations64 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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 Records1 A records, 78 ms lookupPASS
| A | 192.0.66.199 |
| AAAA | — |
| CNAME | — |
| NS | ns-1735.awsdns-24.co.uk, ns-62.awsdns-07.com, ns-665.awsdns-19.net, ns-1055.awsdns-03.org |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | tollbit-domain-verification=48a502ccdc91beb3993a55f15fd37aa9cbc7f61f9ce137067fa9... yahoo-verification-key=kb94WD5iSK/nijzY+omOm+F48FJQR8Pn0qVl72lrEc4= google-site-verification=Y_jMaxVPCA15BFiyKv1rBgs4SzBFNXHN1kGV4xYBbQg google-site-verification=ExXW-kZsF7czGSKVHWR0HDS9vIh1LrZMO0DBjz6H_-c google-site-verification=liDFFAV_7fOAB0R07z0dtYL9DIXuswHHhmfrH1fICHI google-site-verification=f3w5KgK85JM8Y47MCU3cxXZLc-ftt01EVSgjO7MkK-I facebook-domain-verification=yl8a8v1shixtf3c7ccqusvku99x8lx SPF v=spf1 a mx include:amazonses.com include:aspmx.sailthru.com include:_spf.google... google-site-verification=WjKJsZHRR26ZjWWBsm542-8EXiT1tuKCWZM8CFu0I5Y google-site-verification=Bc-Fo_Bx2yrkvqWrqUmj3PAdmPAJCK9n0dhLP4zz5S0 google-site-verification=UYkFTffKCjfiv4mPqitJ1oRVFkZ8aVfmSjsRt2mGuhk fastly-domain-delegation-7hhjhxsvpzz94pnapepu-811002-2024-09-12 google-site-verification=Vyhl0m5U9GcJAZxmA4gTZF8wrQpEAcXOdQ1o0d9fbvs google-site-verification=sjzRjvHDf0PKX-QNqZcv_E0fV6NVsMRBsmdtRpolEAw google-site-verification=4XD95nhD3HqwWlPTW8kxfOyWaFWRg_AR4erlQSd3xYk google-site-verification=sYTODX1d1Z6fMT8UQBXWv1-kOf4vFSF00vOBrNZ2s7g |
| 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.
A+Redirect ChainNo redirects — direct accessPASS
https://futurism.com
9 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://futurism.com | 200 | 9 ms | HTTP/1.1 | nginx |
A+Crawlabilityrobots.txt present, sitemap with 15 URLsPASS
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /preview?*
Disallow: /*/edit$
Disallow: /*/edit/$
Disallow: /edit$
Disallow: /edit/$
User-agent: AmazonAdBot
Allow: /
Sitemap: https://futurism.com/sitemap_index.xml
Sitemap: https://futurism.com/sitemap-news.xml
- https://futurism.com/future-society/prego-pivots-pasta-sauce-microphone
- https://futurism.com/artificial-intelligence/chinese-workers-train-ai-replacements
- https://futurism.com/artificial-intelligence/concern-grows-ai-damaging-think
- https://futurism.com/space/jeff-bezos-new-glenn-failure-nasa-moon
- https://futurism.com/space/nasa-artemis-2-heat-shield-photo-underwater
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefuturism.com — via NameCheap, Inc., 30 years, 1 months old, hosted on WordPress.com (Automattic)PASS
34 days
August 21, 2026
64 days
Issued by Let's Encrypt
30 years, 1 months
Registered August 22, 1996
Not enabled
Protects against DNS spoofing
WordPress.com (Automattic)
ASN AS2635
192.0.66.199
NameCheap, Inc.
Expiry timeline
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
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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