Skip to content
https://webworthit.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
6 PASS 10 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.webworthit.com/
200https://webworthit.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://webworthit.com/

HTTP version does not redirect to HTTPS

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 140.99.254.76 does not match any cert SAN: host.clkdriver.info
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
Multi-Resolver DNS Speed
Action
Mean 223ms across 3 resolvers (spread 246ms)
REVIEW
Mean 223ms across 3 resolvers (spread 246ms)
Info::
Google: 102ms
Got: 102ms via 8.8.8.8:53
Info::
Quad9: 219ms
Got: 219ms via 9.9.9.9:53
Info::
Cloudflare: 348ms
Got: 348ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 246ms (min 102ms / max 348ms)
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.
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
TLS Certificate Expiry & Recommendations
50 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

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
C
CDN & Delivery
Action
Assets on Cloudflare (host api.pagepeeker.com, 6 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host api.pagepeeker.com, 6 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (api.pagepeeker.com, 6 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a3b09eccca30c653-CDG
Info::
Assets on Cloudflare: api.pagepeeker.com (assets: 6), cache DYNAMIC
Got: cf-ray: a3b09eccca30c653-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • api.pagepeeker.com — Cloudflare · assets: 6 · Cache Status: DYNAMIC

Other asset hosts

  • www.networkadspace.com — assets: 3 · not attributed
  • cdnjs.cloudflare.com — assets: 2 · below probe threshold
  • www.downlinebanners.com — assets: 2 · below probe threshold
  • 5xyourteam.com — assets: 1 · below probe threshold
  • downlinehydra.com — assets: 1 · below probe threshold
  • leasedadspace.com — assets: 1 · below probe threshold
  • www.elitedownlineclub.com — assets: 1 · below probe threshold
  • www.google.com — assets: 1 · below probe threshold
  • www.gstatic.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
1 A records, 202 ms lookup
PASS
1 A records, 202 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 140.99.254.76
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.clkdriver.info, ns1.clkdriver.info
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (202 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 202 ms
A140.99.254.76
AAAA—
CNAME—
NSns2.clkdriver.info, ns1.clkdriver.info
MX
0 webworthit.com
TXT
SPF v=spf1 ip4:140.99.254.76 ip4:38.46.218.26 ip4:38.46.218.27 ip4:104.219.234.2 +a ...
CAALookup not available with standard resolver
Resolved in 202 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://webworthit.com

https://webworthit.com

344 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://webworthit.com200344 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 22 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 22 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
webworthit.com — via NameSilo, LLC, 4 years, 2 months old, hosted on AS-GLOBALTELEHOST - GTHost, US
PASS
webworthit.com — via NameSilo, LLC, 4 years, 2 months old, hosted on AS-GLOBALTELEHOST - GTHost, US
Info::
Domain registered until Jul 20, 2027 (10 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: NameSilo, LLC
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: AS-GLOBALTELEHOST - GTHost, US
Got: AS63023
Domain expiry

302 days

July 20, 2027

SSL certificate

50 days

Issued by Let's Encrypt

Domain age

4 years, 2 months

Registered July 20, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AS-GLOBALTELEHOST - GTHost, US

ASN AS63023

140.99.254.76

Registrar

NameSilo, LLC

Unlocked 2 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 NameSilo, LLC
Created July 20, 2022 (4 years, 2 months ago)
Expires July 20, 2027 (10 months)
Last Updated July 21, 2026
Name Servers ns1.clkdriver.info, ns2.clkdriver.info
DNSSEC Not enabled
Hosting
IP Address 140.99.254.76
ASN AS63023 (AS-GLOBALTELEHOST - GTHost, US)
Provider AS-GLOBALTELEHOST - GTHost, US
Data source: rdap (0.4s)

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

A
HTTP Probe Timing
Total 655 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
199 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
95 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
100 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
561 ms
Total Time Total request time from DNS lookup through full response.
655 ms

Connection waterfall

DNS Lookup 199 ms TCP Connect 95 ms TLS Handshake 100 ms Server Processing 167 ms Content Transfer 94 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback