Skip to content
https://siteworth.co

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
7
PASS
8
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
8 PASS 7 REVIEW 2 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.siteworth.co/
200https://siteworth.co/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://siteworth.co/

HTTP version does not redirect to HTTPS

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
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 192.185.24.60 does not match any cert SAN: 192-185-24-60.unifiedlayer.com
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
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
87 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

87
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
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, 156 ms lookup
PASS
1 A records, 156 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.185.24.60
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: ns205.websitewelcome.com, ns206.websitewelcome.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 156 ms
Got: 156 ms
A192.185.24.60
AAAA—
CNAME—
NSns205.websitewelcome.com, ns206.websitewelcome.com
MX
0 mail.siteworth.co
TXT
SPF v=spf1 a mx include:websitewelcome.com ~all
CAALookup not available with standard resolver
Resolved in 156 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 88ms across 3 resolvers (spread 42ms)
PASS
Mean 88ms across 3 resolvers (spread 42ms)
Info::
Cloudflare: 73ms
Got: 73ms via 1.1.1.1:53
Info::
Quad9: 77ms
Got: 77ms via 9.9.9.9:53
Info::
Google: 115ms
Got: 115ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://siteworth.co

https://siteworth.co

440 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://siteworth.co200440 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 21974 URLs
PASS
robots.txt present, sitemap with 21974 URLs
Info::
robots.txt is present
Got: 179 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21974 entries
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 179 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# robotstxt.org/

User-agent: *
Disallow: /admin/
Disallow: /core/
Disallow: /theme/
Disallow: /langs/
Disallow: /site_snapshot/
Disallow: /oauth/
Disallow: /mail/
Disallow: /out/
sitemap.xml 200 OK
Type URL Set URLs 21974 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
siteworth.co — via GoDaddy.com, LLC, 11 years, 2 months old
PASS
siteworth.co — via GoDaddy.com, LLC, 11 years, 2 months old
Info::
Domain registered until May 6, 2027 (11 months remaining)
Info::
Registrar: GoDaddy.com, LLC
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Domain expiry

345 days

May 6, 2027

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

11 years, 2 months

Registered May 7, 2015

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

192.185.24.60

Registrar

GoDaddy.com, LLC

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar GoDaddy.com, LLC
Created May 7, 2015 (11 years, 2 months ago)
Expires May 6, 2027 (11 months)
Last Updated May 7, 2026
Name Servers ns205.websitewelcome.com, ns206.websitewelcome.com
Registrant Domains By Proxy, LLC
Hosting
IP Address 192.185.24.60
Data source: whois (0.9s)

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

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

Connection waterfall

DNS Lookup 136 ms TCP Connect 64 ms TLS Handshake 67 ms Server Processing 170 ms Content Transfer 1 ms
A+
Health Check Endpoint
Health endpoint at https://siteworth.co/health (HTTP 200)
PASS
Health endpoint at https://siteworth.co/health (HTTP 200)
Info::
Public health endpoint at https://siteworth.co/health
Got: https://siteworth.co/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback