Skip to content
https://tahri.technology

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
5
PASS
11
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
11 PASS 5 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:3033::6815:3765, 2606:4700:3033::ac43:9375
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3033::6815:3765]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2606:4700:3033::6815:3765, 2606:4700:3033::ac43:9375 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
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.55.101: lookup 104.21.55.101: 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.147.117: lookup 172.67.147.117: 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:3033::6815:3765: lookup 2606:4700:3033::6815:3765: 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:3033::ac43:9375: lookup 2606:4700:3033::ac43:9375: 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
47 days until leaf cert expires — 1 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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, 19 ms lookup
PASS
2 A records, 19 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.55.101, 172.67.147.117
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3033::6815:3765, 2606:4700:3033::ac43:9375
Info::
2 nameserver(s) configured
Got: nile.ns.cloudflare.com, meera.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 19 ms
Got: 19 ms
A104.21.55.101, 172.67.147.117
AAAA2606:4700:3033::6815:3765, 2606:4700:3033::ac43:9375
CNAME
NSnile.ns.cloudflare.com, meera.ns.cloudflare.com
MX
16 route3.mx.cloudflare.net
56 route1.mx.cloudflare.net
72 route2.mx.cloudflare.net
TXT
SPF v=spf1 a mx include:_spf.google.com include:_spf.smtp.mailtrap.live include:_spf...
CAALookup not available with standard resolver
Resolved in 19 ms
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 27ms)
PASS
Mean 20ms across 3 resolvers (spread 27ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Quad9: 27ms
Got: 27ms via 9.9.9.9:53
Info::
Google: 30ms
Got: 30ms 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://tahri.technology

https://tahri.technology

88 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tahri.technology20088 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 110 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 110 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# allow crawling everything by default
User-agent: *
Disallow:

Sitemap: https://tahri.technology/sitemap.xml

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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.tahri.technology/
200https://tahri.technology/

Preferred variant: non-www

HTTP → HTTPS

301http://tahri.technology/ https://tahri.technology/

Consistent

A+
Domain Intelligence
tahri.technology — via Cloudflare, Inc, 3 years, 5 months old
PASS
tahri.technology — via Cloudflare, Inc, 3 years, 5 months old
Info::
Domain registered until Mar 13, 2027 (7 months remaining)
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

216 days

March 13, 2027

SSL certificate

47 days

Issued by Google Trust Services

Domain age

3 years, 5 months

Registered March 13, 2023

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3033::6815:3765

Registrar

Cloudflare, Inc

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc
Created March 13, 2023 (3 years, 5 months ago)
Expires March 13, 2027 (7 months)
Last Updated February 16, 2026
Name Servers meera.ns.cloudflare.com, nile.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700:3033::6815:3765
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 28 ms TCP Connect 2 ms TLS Handshake 11 ms Server Processing 72 ms Content Transfer 28 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a2303ff3ae3f30f5-EWR
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a2303ff3ae3f30f5-EWR
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 2 header(s)
Got: age=0, cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback