Skip to content
https://claysys.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
17
11 PASS 6 REVIEW
C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
C
Reverse DNS
Action
0/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 172.67.75.16: lookup 172.67.75.16: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.26.3.184: lookup 104.26.3.184: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.26.2.184: lookup 104.26.2.184: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:3b8: lookup 2606:4700:20::681a:3b8: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:2b8: lookup 2606:4700:20::681a:2b8: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::ac43:4b10: lookup 2606:4700:20::ac43:4b10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
63 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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 & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a51a07db9e90792e-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a51a07db9e90792e-CDG
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
3 A records, 43 ms lookup
PASS
3 A records, 43 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 172.67.75.16, 104.26.3.184, 104.26.2.184
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:3b8, 2606:4700:20::681a:2b8, 2606:4700:20::ac43:4b10
Info::
2 nameserver(s) configured
Got: marissa.ns.cloudflare.com, boyd.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 43 ms
Got: 43 ms
A172.67.75.16, 104.26.3.184, 104.26.2.184
AAAA2606:4700:20::681a:3b8, 2606:4700:20::681a:2b8, 2606:4700:20::ac43:4b10
CNAME—
NSmarissa.ns.cloudflare.com, boyd.ns.cloudflare.com
MX
0 claysys-com.mail.protection.outlook.com
TXT
kqjcf5985pudfq8sdd2pmif8d1
31hsvasrjdudomtbo7vbpbjf65
fn4i9cf9ruhcns97l32kuo55cj
SPF v=spf1 include:spf.protection.outlook.com -all
MS=ms38899055
nt5a293rqfma2q7vg5g494vbpn
5f24idihjqdbf522o0gbj41k1m
MS=4FFF11ABEFC44D282C2DF172623D33688774E716
CAALookup not available with standard resolver
Resolved in 43 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: comodoca.com, digicert.com, godaddy.com, letsencrypt.org, pki.goog, ssl.com | issuewild: comodoca.com, digicert.com, godaddy.com, letsencrypt.org, pki.goog, ssl.com
PASS
issue: comodoca.com, digicert.com, godaddy.com, letsencrypt.org, pki.goog, ssl.com | issuewild: comodoca.com, digicert.com, godaddy.com, letsencrypt.org, pki.goog, ssl.com
Info::
CAA issue tag present — authorized CA(s): comodoca.com, digicert.com, godaddy.com, letsencrypt.org, pki.goog, ssl.com
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+
Multi-Resolver DNS Speed
Mean 33ms across 3 resolvers (spread 13ms)
PASS
Mean 33ms across 3 resolvers (spread 13ms)
Info::
Quad9: 28ms
Got: 28ms via 9.9.9.9:53
Info::
Google: 30ms
Got: 30ms via 8.8.8.8:53
Info::
Cloudflare: 41ms
Got: 41ms via 1.1.1.1:53
A+
Redirect Chain
0 redirect(s), 94 ms total
PASS
0 redirect(s), 94 ms total

https://claysys.com

94 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://claysys.com40394 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:3b8, 2606:4700:20::681a:2b8, 2606:4700:20::ac43:4b10
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:3b8, 2606:4700:20::681a:2b8, 2606:4700:20::ac43:4b10 Connection Reachable (17 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 431 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 431 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Disallow: /wp-includes/

Disallow: /thankyou/

Disallow: /rpagenie/

Disallow: /RPAGenie/

Allow: /app/themes/claysys-2019/assets/scripts/

Allow: /app/themes/claysys-2019/assets/styles/

Noindex: /app/themes/claysys-2019/assets/scripts/
Noindex: /app/themes/claysys-2019/assets/styles/
Disallow: /app/themes/claysys-2019/captcha_code.php  

Sitemap: https://www.claysys.com/sitemap_index.xml
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

403https://www.claysys.com/
200https://claysys.com/

HTTP → HTTPS

301http://claysys.com/ → https://claysys.com/

Consistent

A+
Domain Intelligence
claysys.com — via IONOS SE, 16 years, 6 months old
PASS
claysys.com — via IONOS SE, 16 years, 6 months old
Info::
Domain registered until Jun 30, 2027 (8 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: IONOS SE
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

233 days

June 30, 2027

SSL certificate

63 days

Issued by Google Trust Services

Domain age

16 years, 6 months

Registered June 30, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:3b8

Registrar

IONOS SE

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 IONOS SE
Created June 30, 2010 (16 years, 6 months ago)
Expires June 30, 2027 (8 months)
Last Updated July 1, 2026
Name Servers boyd.ns.cloudflare.com, marissa.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:3b8
Data source: rdap (0.2s)

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 130 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
33 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
130 ms
Total Time Total request time from DNS lookup through full response.
131 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 17 ms TLS Handshake 33 ms Server Processing 40 ms Content Transfer 0 ms
A+
Health Check Endpoint
Auth-protected health endpoint at https://claysys.com/health (HTTP 403)
PASS
Auth-protected health endpoint at https://claysys.com/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://claysys.com/health
Got: https://claysys.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