Skip to content
https://www.kapuli.ai

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
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/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 99.86.12.24 does not match any cert SAN: server-99-86-12-24.lhr95.r.cloudfront.net
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 99.86.12.115 does not match any cert SAN: server-99-86-12-115.lhr95.r.cloudfront.net
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 99.86.12.86 does not match any cert SAN: server-99-86-12-86.lhr95.r.cloudfront.net
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 99.86.12.111 does not match any cert SAN: server-99-86-12-111.lhr95.r.cloudfront.net
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 lookup failed for 2600:9000:209d:de00:4:9d1c:7d00:93a1: lookup 2600:9000:209d:de00:4:9d1c:7d00:93a1: 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 2600:9000:209d:8600:4:9d1c:7d00:93a1: lookup 2600:9000:209d:8600:4:9d1c:7d00:93a1: 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 2600:9000:209d:ba00:4:9d1c:7d00:93a1: lookup 2600:9000:209d:ba00:4:9d1c:7d00:93a1: 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 2600:9000:209d:1400:4:9d1c:7d00:93a1: lookup 2600:9000:209d:1400:4:9d1c:7d00:93a1: 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 2600:9000:209d:9c00:4:9d1c:7d00:93a1: lookup 2600:9000:209d:9c00:4:9d1c:7d00:93a1: 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 2600:9000:209d:3a00:4:9d1c:7d00:93a1: lookup 2600:9000:209d:3a00:4:9d1c:7d00:93a1: 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 2600:9000:209d:5800:4:9d1c:7d00:93a1: lookup 2600:9000:209d:5800:4:9d1c:7d00:93a1: 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 2600:9000:209d:200:4:9d1c:7d00:93a1: lookup 2600:9000:209d:200:4:9d1c:7d00:93a1: 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
HTTP Probe Timing
Total 994 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
64 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
735 ms
Total Time Total request time from DNS lookup through full response.
995 ms

Connection waterfall

DNS Lookup 64 ms TCP Connect 25 ms TLS Handshake 36 ms Server Processing 610 ms Content Transfer 260 ms
B
TLS Certificate Expiry & Recommendations
105 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

105
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
AWS CloudFront (Error from cloudfront)
REVIEW
AWS CloudFront (Error from cloudfront)
Info::
Document is served via AWS CloudFront CDN (edge: LHR95-P3)
Got: delegation d1psj6rrovo2k4.cloudfront.net
Info::
CDN cache status: Error from cloudfront
Document served via CDN: AWS CloudFront
Provider AWS CloudFront Cache Status Error from cloudfront Evidence delegation d1psj6rrovo2k4.cloudfront.net
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
4 A records, 39 ms lookup
PASS
4 A records, 39 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 99.86.12.24, 99.86.12.115, 99.86.12.86, 99.86.12.111
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:209d:de00:4:9d1c:7d00:93a1, 2600:9000:209d:8600:4:9d1c:7d00:93a1, 2600:9000:209d:ba00:4:9d1c:7d00:93a1, 2600:9000:209d:1400:4:9d1c:7d00:93a1, 2600:9000:209d:9c00:4:9d1c:7d00:93a1, 2600:9000:209d:3a00:4:9d1c:7d00:93a1, 2600:9000:209d:5800:4:9d1c:7d00:93a1, 2600:9000:209d:200:4:9d1c:7d00:93a1
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: d1psj6rrovo2k4.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1227.awsdns-25.org, ns-909.awsdns-49.net, ns-430.awsdns-53.com, ns-1981.awsdns-55.co.uk
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 39 ms
Got: 39 ms
A99.86.12.24, 99.86.12.115, 99.86.12.86, 99.86.12.111
AAAA2600:9000:209d:de00:4:9d1c:7d00:93a1, 2600:9000:209d:8600:4:9d1c:7d00:93a1, 2600:9000:209d:ba00:4:9d1c:7d00:93a1, 2600:9000:209d:1400:4:9d1c:7d00:93a1, 2600:9000:209d:9c00:4:9d1c:7d00:93a1, 2600:9000:209d:3a00:4:9d1c:7d00:93a1, 2600:9000:209d:5800:4:9d1c:7d00:93a1, 2600:9000:209d:200:4:9d1c:7d00:93a1
CNAMEd1psj6rrovo2k4.cloudfront.net
NSns-1227.awsdns-25.org, ns-909.awsdns-49.net, ns-430.awsdns-53.com, ns-1981.awsdns-55.co.uk
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 39 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
CNAME points at managed service(s) — verify configuration
PASS
CNAME points at managed service(s) — verify configuration
Info::
CNAME targets AWS CloudFront — verify ownership
CNAME targets CloudFront. Distribution names are GUID-style so accidental re-registration is unlikely, but a deleted distribution will return errors. Verify the CloudFront distribution is still active.
Got: d1psj6rrovo2k4.cloudfront.net
A+
Multi-Resolver DNS Speed
Mean 48ms across 3 resolvers (spread 20ms)
PASS
Mean 48ms across 3 resolvers (spread 20ms)
Info::
Quad9: 41ms
Got: 41ms via 9.9.9.9:53
Info::
Cloudflare: 43ms
Got: 43ms via 1.1.1.1:53
Info::
Google: 61ms
Got: 61ms 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://www.kapuli.ai

https://www.kapuli.ai

654 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.kapuli.ai200654 msHTTP/1.1AmazonS3
A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2600:9000:209d:de00:4:9d1c:7d00:93a1, 2600:9000:209d:8600:4:9d1c:7d00:93a1, 2600:9000:209d:ba00:4:9d1c:7d00:93a1, 2600:9000:209d:1400:4:9d1c:7d00:93a1, 2600:9000:209d:9c00:4:9d1c:7d00:93a1, 2600:9000:209d:3a00:4:9d1c:7d00:93a1, 2600:9000:209d:5800:4:9d1c:7d00:93a1, 2600:9000:209d:200:4:9d1c:7d00:93a1
Got: 25 ms connect
IPv6 Ready
AAAA Records 2600:9000:209d:de00:4:9d1c:7d00:93a1, 2600:9000:209d:8600:4:9d1c:7d00:93a1, 2600:9000:209d:ba00:4:9d1c:7d00:93a1, 2600:9000:209d:1400:4:9d1c:7d00:93a1, 2600:9000:209d:9c00:4:9d1c:7d00:93a1, 2600:9000:209d:3a00:4:9d1c:7d00:93a1, 2600:9000:209d:5800:4:9d1c:7d00:93a1, 2600:9000:209d:200:4:9d1c:7d00:93a1 Connection Reachable (25 ms)
A+
Crawlability
robots.txt present, sitemap with 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 655 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 655 B Sitemaps referenced 1 User-agents PerplexityBot, OAI-SearchBot, Claude-SearchBot, Perplexity-User, Google-Extended, Applebot-Extended, Applebot, Bingbot, *, ChatGPT-User, GPTBot, ClaudeBot, Claude-User Blocking No — crawling allowed
# robots.txt, https://www.kapuli.ai/
# Explicitly welcome AI assistant + search crawlers so Kapuli is eligible
# to be read, indexed, and cited in AI-generated answers.

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: Applebot
Allow: /

User-agent: Bingbot
Allow: /

User-agent: *
Allow: /

Sitemap: https://www.kapuli.ai/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 19 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.kapuli.ai/
302https://kapuli.ai/

Preferred variant: www

HTTP → HTTPS

301http://www.kapuli.ai/ → https://www.kapuli.ai/

Consistent

A+
Domain Intelligence
kapuli.ai — via InternetX, 4 months old
PASS
kapuli.ai — via InternetX, 4 months old
Info::
Domain registered until May 18, 2028 (1 years, 8 months remaining)
Info::
Domain is only 4 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered May 18, 2026
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: InternetX
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

603 days

May 18, 2028

SSL certificate

105 days

Issued by Amazon

Domain age

4 months

Registered May 18, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2607:f1c0:100f:f000::200

Registrar

InternetX

Unlocked 4 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar InternetX
Created May 18, 2026 (4 months ago)
Expires May 18, 2028 (1 years, 8 months)
Last Updated August 11, 2026
Name Servers ns1067.ui-dns.com, ns1094.ui-dns.de, ns1096.ui-dns.org, ns1084.ui-dns.biz
DNSSEC Not enabled
Registrant Admin Contact
Hosting
IP Address 2607:f1c0:100f:f000::200
Data source: rdap (1.4s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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+
CDN Cache Observability
Cache state: ERROR
PASS
Cache state: ERROR
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Error from cloudfront
A+
Health Check Endpoint
Health endpoint at https://www.kapuli.ai/health (HTTP 200)
PASS
Health endpoint at https://www.kapuli.ai/health (HTTP 200)
Info::
Public health endpoint at https://www.kapuli.ai/health
Got: https://www.kapuli.ai/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback