Skip to content
https://the-spider.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
3
REVIEW
6
PASS
8
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
8 PASS 6 REVIEW 3 FIX
F
DNSSEC
Action
DS at parent but zone has no DNSKEY
FIX
DS at parent but zone has no DNSKEY
Critical::
Parent zone has DS record but the zone publishes no DNSKEY
The registry advertises this domain as signed (DS record present) but the zone returns no DNSKEY records. Validating resolvers will SERVFAIL. Either republish the DNSKEY records or remove the DS record at the registrar.
D
Multi-Resolver DNS Speed
Action
Mean 516ms across 3 resolvers (spread 709ms)
FIX
Mean 516ms across 3 resolvers (spread 709ms)
Info::
Cloudflare: 140ms
Got: 140ms via 1.1.1.1:53
Info::
Quad9: 560ms
Got: 560ms via 9.9.9.9:53
Info::
Google: 849ms
Got: 849ms via 8.8.8.8:53
Info::
High latency spread between resolvers: 709ms (min 140ms / max 849ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
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.

B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 159.203.85.91 does not match any cert SAN: www.smoothnet.org
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2604:a880:800:10::ac8:f001 does not match any cert SAN: www.smoothnet.org
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 14 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 14 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
HTTP Probe Timing
Total 1485 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
921 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
111 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
121 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.27 s
Total Time Total request time from DNS lookup through full response.
1.49 s

Connection waterfall

DNS Lookup 921 ms TCP Connect 111 ms TLS Handshake 121 ms Server Processing 117 ms Content Transfer 216 ms
B
TLS Certificate Expiry & Recommendations
69 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A
DNS Records
1 A records, 961 ms lookup
PASS
1 A records, 961 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 159.203.85.91
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2604:a880:800:10::ac8:f001
Info::
2 nameserver(s) configured
Got: ns1.smoothnet.org, ns2.smoothnet.org
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (961 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 961 ms
A159.203.85.91
AAAA2604:a880:800:10::ac8:f001
CNAME—
NSns1.smoothnet.org, ns2.smoothnet.org
MX
0 thespider-com0i.mail.protection.outlook.com
TXT
SPF v=spf1 ip4:104.131.24.164 ip6:2604:a880:800:10::3ab:4001 include:spf.protection....
CAALookup not available with standard resolver
Resolved in 961 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: letsencrypt.org
PASS
issue: letsencrypt.org
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://the-spider.com

https://the-spider.com

359 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://the-spider.com200359 msHTTP/1.1Apache
A+
IPv6 Readiness
IPv6 reachable (117 ms)
PASS
IPv6 reachable (117 ms)
Info::
IPv6 is configured and reachable at 2604:a880:800:10::ac8:f001
Got: 117 ms connect
IPv6 Ready
AAAA Records 2604:a880:800:10::ac8:f001 Connection Reachable (117 ms)
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

307https://www.the-spider.com/
200https://the-spider.com/

HTTP → HTTPS

307http://the-spider.com/ → https://the-spider.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
the-spider.com — via Spaceship, Inc., 21 years, 2 months old
PASS
the-spider.com — via Spaceship, Inc., 21 years, 2 months old
Info::
Domain registered until Jun 20, 2030 (4 years, 2 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Spaceship, 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

1497 days

June 20, 2030

SSL certificate

69 days

Issued by Let's Encrypt

Domain age

21 years, 2 months

Registered June 20, 2005

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2604:a880:800:10::ac8:f001

Registrar

Spaceship, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Spaceship, Inc.
Created June 20, 2005 (21 years, 2 months ago)
Expires June 20, 2030 (4 years, 2 months)
Last Updated December 21, 2025
Name Servers ns1.smoothnet.org, ns2.smoothnet.org
DNSSEC Enabled
Hosting
IP Address 2604:a880:800:10::ac8:f001
Data source: rdap (0.4s)

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+
Health Check Endpoint
Health endpoint at https://the-spider.com/health (HTTP 200)
PASS
Health endpoint at https://the-spider.com/health (HTTP 200)
Info::
Public health endpoint at https://the-spider.com/health
Got: https://the-spider.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback