Skip to content
https://hellosindh.ai

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
4
PASS
13
INFO
0
Probed from Madrid, Spain
307 Temporary Redirect
Checks
17
13 PASS 4 REVIEW
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 188.114.96.2: lookup 188.114.96.2: 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 188.114.97.2: lookup 188.114.97.2: 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 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: 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 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: 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
67 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
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
2 A records, 47 ms lookup
PASS
2 A records, 47 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.96.2, 188.114.97.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3121::2, 2a06:98c1:3120::2
Info::
2 nameserver(s) configured
Got: adi.ns.cloudflare.com, henry.ns.cloudflare.com
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: 47 ms
Got: 47 ms
A188.114.96.2, 188.114.97.2
AAAA2a06:98c1:3121::2, 2a06:98c1:3120::2
CNAME—
NSadi.ns.cloudflare.com, henry.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 47 ms

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
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Multi-Resolver DNS Speed
Mean 20ms across 3 resolvers (spread 17ms)
PASS
Mean 20ms across 3 resolvers (spread 17ms)
Info::
Quad9: 11ms
Got: 11ms via 9.9.9.9:53
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 470 ms total
PASS
1 redirect(s), 470 ms total
Info::
Single redirect
Got: https://hellosindh.ai → https://hellosindh.ai/en (307)

https://hellosindh.ai

260 ms · HTTP/1.1

307

https://hellosindh.ai/en

210 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hellosindh.ai307260 msHTTP/1.1cloudflare
2https://hellosindh.ai/en200210 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3121::2, 2a06:98c1:3120::2
Got: 17 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3121::2, 2a06:98c1:3120::2 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 439 URLs
PASS
robots.txt present, sitemap with 439 URLs
Info::
robots.txt is present
Got: 99 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 439 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 99 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /api/
Disallow: /app/

Sitemap: https://hellosindh.ai/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 439 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::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

308https://www.hellosindh.ai/
200https://hellosindh.ai/

HTTP → HTTPS

301http://hellosindh.ai/ → https://hellosindh.ai/

Consistent

A+
Domain Intelligence
hellosindh.ai — via Cloudflare, Inc, 22 days old
PASS
hellosindh.ai — via Cloudflare, Inc, 22 days old
Info::
Domain registered until Oct 19, 2028 (1 years, 11 months remaining)
Info::
Domain is only 22 days 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 Oct 19, 2026
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, 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.
Domain expiry

707 days

October 19, 2028

SSL certificate

67 days

Issued by Let's Encrypt

Domain age

22 days

Registered October 19, 2026

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3120::2

Registrar

Cloudflare, Inc

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc
Created October 19, 2026 (22 days ago)
Expires October 19, 2028 (1 years, 11 months)
Last Updated October 24, 2026
Name Servers henry.ns.cloudflare.com, adi.ns.cloudflare.com
DNSSEC Enabled
Registrant DATA REDACTED
Hosting
IP Address 2a06:98c1:3120::2
Data source: rdap (0.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.

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 623 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
34 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.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
623 ms
Total Time Total request time from DNS lookup through full response.
623 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 548 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a58cc2adcbd1d09b-CDG
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a58cc2adcbd1d09b-CDG
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
A+
Health Check Endpoint
Health endpoint at https://hellosindh.ai/api/health (HTTP 200)
PASS
Health endpoint at https://hellosindh.ai/api/health (HTTP 200)
Info::
Public health endpoint at https://hellosindh.ai/api/health
Got: https://hellosindh.ai/api/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback