Skip to content
https://aiagentskills.net

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Santa Clara, United States
500 Internal Server Error
Checks
17
7 PASS 9 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:3035::ac43:c125, 2606:4700:3030::6815:1495
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3035::ac43:c125]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:3035::ac43:c125, 2606:4700:3030::6815:1495 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.21.20.149: lookup 104.21.20.149: 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 172.67.193.37: lookup 172.67.193.37: 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:3035::ac43:c125: lookup 2606:4700:3035::ac43:c125: 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:3030::6815:1495: lookup 2606:4700:3030::6815:1495: 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 500 Expected: 301 redirect to HTTPS

www / non-www

https://www.aiagentskills.net/
200https://aiagentskills.net/

HTTP → HTTPS

500http://aiagentskills.net/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
41 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

41
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 & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: a31570975997fca9-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: a31570975997fca9-SJC
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
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.20.149, 172.67.193.37
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3035::ac43:c125, 2606:4700:3030::6815:1495
Info::
2 nameserver(s) configured
Got: lee.ns.cloudflare.com, liberty.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 9 ms
Got: 9 ms
A104.21.20.149, 172.67.193.37
AAAA2606:4700:3035::ac43:c125, 2606:4700:3030::6815:1495
CNAME
NSlee.ns.cloudflare.com, liberty.ns.cloudflare.com
MX
10 eforward3.registrar-servers.com
10 eforward1.registrar-servers.com
10 eforward2.registrar-servers.com
15 eforward4.registrar-servers.com
20 eforward5.registrar-servers.com
TXT
google-site-verification=dYQMTxiRZqs2v_H-u2eITdqCb4wkdOdbLwNe_m50FV0
SPF v=spf1 include:spf.efwd.registrar-servers.com ~all
yandex-verification: c1a2e212a8032493
CAALookup not available with standard resolver
Resolved in 9 ms
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 9ms across 3 resolvers (spread 17ms)
PASS
Mean 9ms across 3 resolvers (spread 17ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Quad9: 4ms
Got: 4ms via 9.9.9.9:53
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
A+
Redirect Chain
0 redirect(s), 220 ms total
PASS
0 redirect(s), 220 ms total

https://aiagentskills.net

220 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aiagentskills.net500220 msHTTP/1.1cloudflare
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 829 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 829 B Sitemaps referenced 1 User-agents GPTBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Google-Extended, Googlebot, Applebot, *, OAI-SearchBot, Claude-SearchBot, Perplexity-User, Bingbot Blocking No — crawling allowed
User-Agent: *
Allow: /
Allow: /llms.txt
Allow: /api/sitemap/
Allow: /sitemap.xml
Allow: /sitemap-static.xml
Disallow: /*?*q=
Disallow: /search
Disallow: /api/
Disallow: /admin/
Disallow: /settings/
Disallow: /activity/
Disallow: /chat/

User-Agent: GPTBot
User-Agent: ChatGPT-User
User-Agent: OAI-SearchBot
User-Agent: ClaudeBot
User-Agent: Claude-User
User-Agent: Claude-SearchBot
User-Agent: PerplexityBot
User-Agent: Perplexity-User
User-Agent: Google-Extended
User-Agent: Googlebot
User-Agent: Bingbot
User-Agent: Applebot
Allow: /
Allow: /llms.txt
Allow: /api/sitemap/
Allow: /sitemap.xml
Allow: /sitemap-static.xml
Disallow: /*?*q=
Disallow: /search
Disallow: /api/
Disallow: /admin/
Disallow: /settings/
Disallow: /activity/
Disallow: /chat/

Host: https://aiagentskills.net
Sitemap: https://aiagentskills.net/sitemap.xml

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
Domain Intelligence
aiagentskills.net — via NameCheap, Inc., 7 months old, hosted on Cloudflare
PASS
aiagentskills.net — via NameCheap, Inc., 7 months old, hosted on Cloudflare
Info::
Domain registered until Jan 9, 2027 (4 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: NameCheap, 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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

135 days

January 9, 2027

SSL certificate

41 days

Issued by Google Trust Services

Domain age

7 months

Registered January 9, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.21.20.149

Registrar

NameCheap, Inc.

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 NameCheap, Inc.
Created January 9, 2026 (7 months ago)
Expires January 9, 2027 (4 months)
Last Updated January 12, 2026
Name Servers lee.ns.cloudflare.com, liberty.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.21.20.149
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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 423 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
408 ms
Total Time Total request time from DNS lookup through full response.
423 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 4 ms TLS Handshake 8 ms Server Processing 391 ms Content Transfer 15 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback