Skip to content
https://ldns.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
9 PASS 7 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:3030::6815:503f, 2606:4700:3030::ac43:aebb
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3030::6815:503f]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:3030::6815:503f, 2606:4700:3030::ac43:aebb 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 172.67.174.187: lookup 172.67.174.187: 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.21.80.63: lookup 104.21.80.63: 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:503f: lookup 2606:4700:3030::6815:503f: 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::ac43:aebb: lookup 2606:4700:3030::ac43:aebb: 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

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: a0e918dd585d8462-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: a0e918dd585d8462-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, 11 ms lookup
PASS
2 A records, 11 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.174.187, 104.21.80.63
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3030::6815:503f, 2606:4700:3030::ac43:aebb
Info::
2 nameserver(s) configured
Got: nola.ns.cloudflare.com, david.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 11 ms
Got: 11 ms
A172.67.174.187, 104.21.80.63
AAAA2606:4700:3030::6815:503f, 2606:4700:3030::ac43:aebb
CNAME—
NSnola.ns.cloudflare.com, david.ns.cloudflare.com
MX
34 route1.mx.cloudflare.net
54 route2.mx.cloudflare.net
88 route3.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
google-site-verification=J0p_ZyhRIkPsRPHtD65iZqzl_CAU_KUlekmCP3vjGX4
CAALookup not available with standard resolver
Resolved in 11 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 12ms across 3 resolvers (spread 17ms)
PASS
Mean 12ms across 3 resolvers (spread 17ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Quad9: 13ms
Got: 13ms via 9.9.9.9:53
Info::
Google: 20ms
Got: 20ms 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://ldns.com

https://ldns.com

175 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ldns.com200175 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 490 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
Sitemap index with 11 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 490 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# LDNS — robots.txt
# Free, public DNS / RDAP / email / server / security tools.
# Everything is crawlable — no admin areas, no auth.

User-agent: *
Allow: /
Disallow: /api/

Sitemap: https://ldns.com/sitemap.xml

# Cloudflare content signals — explicit permissions so AI/search vendors
# know what's allowed. (search = yes / ai-input = yes / ai-train = no)
# See https://developers.cloudflare.com/cache/concepts/content-signals/
Content-Signal: search=yes, ai-input=yes, ai-train=no
sitemap.xml 200 OK
Type Sitemap Index URLs 11 entries Valid XML Yes
Child Sitemaps:
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.ldns.com/
200https://ldns.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
ldns.com — via Dynadot Inc, 30 years, 5 months old, hosted on Cloudflare
PASS
ldns.com — via Dynadot Inc, 30 years, 5 months old, hosted on Cloudflare
Info::
Domain registered until Jun 26, 2027 (1 years remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Dynadot 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

349 days

June 26, 2027

SSL certificate

47 days

Issued by Google Trust Services

Domain age

30 years, 5 months

Registered June 27, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.21.80.63

Registrar

Dynadot 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 Dynadot Inc
Created June 27, 1996 (30 years, 5 months ago)
Expires June 26, 2027 (1 years)
Last Updated June 4, 2026
Name Servers david.ns.cloudflare.com, nola.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 104.21.80.63
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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 190 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
21 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
5 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
190 ms
Total Time Total request time from DNS lookup through full response.
191 ms

Connection waterfall

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

Send Feedback