Skip to content
https://ansi.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
5 PASS 4 REVIEW
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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 No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ansi.org/
200https://ansi.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ansi.org/ https://ansi.org/

Consistent

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

Certificate validity

33
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: CDG)
Got: cf-ray: 9f077333993475de-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f077333993475de-CDG
A+
DNS Records
2 A records, 37 ms lookup
PASS
2 A records, 37 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.30.168, 104.18.31.168
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:1ea8, 2606:4700::6812:1fa8
Info::
2 nameserver(s) configured
Got: yolanda.ns.cloudflare.com, clark.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 37 ms
Got: 37 ms
A104.18.30.168, 104.18.31.168
AAAA2606:4700::6812:1ea8, 2606:4700::6812:1fa8
CNAME
NSyolanda.ns.cloudflare.com, clark.ns.cloudflare.com
MX
0 us-smtp-inbound-1.mimecast.com
1 us-smtp-inbound-2.mimecast.com
TXT
55a9372ada8b21d82bfca39fd1ac6207
dt/SDOSwNCMr3VTCsQ9q6CO3LQbvkCzmfEOdTcA/Wm5lUchxSN1rX7RCzmLlCYDqe06YcdIg8VTYoFob...
cisco-ci-domain-verification=3106fcf735a5ce72fee8c00686db8b5cb135d60c900c01a6def...
healthloq-verification-72b5e497-e3b2-4c73-bebc-f590a1450e92
PaehinFvuPP2yOvJVSqClbsC8IM0j2ZrFyeT1CSRAFcgUqJM9TZdh7sEowSuMBzklCRltmtJhPQ0T0a4...
google-site-verification=aorQPyFlbi8PPPXMC-9f2ju745WbqqSlnXTjGKalRZc
SPF v=spf1 include:us._netblocks.mimecast.com include:jangomail.com include:customer...
_globalsign-domain-verification=9QISJ1PWjBboJi0YS52RcKD1_o0MQEkxF7f238M85u
0ed1fe018ae9dcd0841ef949c3875b54b1135bdbac
google-site-verification=4-2Z66HjHyylqmH2ie_Sg4P_gG8iyOBCXGdrsqln1C8
MS=B7096F758C6EF97D151FF27BB81AF60C781E00D9
_globalsign-domain-verification=Nmc8CYKUg3qLcDMfcGc3wKVxPD9WiI--6jDS0eAInH
CAALookup not available with standard resolver
Resolved in 37 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
0 redirect(s), 64 ms total
PASS
0 redirect(s), 64 ms total

https://ansi.org

64 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ansi.org40364 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:1ea8, 2606:4700::6812:1fa8
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:1ea8, 2606:4700::6812:1fa8 Connection Reachable (17 ms)
A+
Domain Intelligence
ansi.org — via GoDaddy.com, LLC, 31 years, 10 months old
PASS
ansi.org — via GoDaddy.com, LLC, 31 years, 10 months old
Info::
Domain registered until Nov 14, 2030 (4 years, 7 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: GoDaddy.com, LLC
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

1581 days

November 14, 2030

SSL certificate

33 days

Issued by Let's Encrypt

Domain age

31 years, 10 months

Registered November 15, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:1ea8

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created November 15, 1994 (31 years, 10 months ago)
Expires November 14, 2030 (4 years, 7 months)
Last Updated June 10, 2024
Name Servers clark.ns.cloudflare.com, yolanda.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:1ea8
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 38 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 22 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback