Skip to content
https://nami.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
1
REVIEW
3
PASS
4
INFO
1
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 3 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:20::681a:ed0, 2606:4700:20::681a:fd0, 2606:4700:20::ac43:4b25
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:20::681a:ed0]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:20::681a:ed0, 2606:4700:20::681a:fd0, 2606:4700:20::ac43:4b25 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
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.nami.org/
200https://nami.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nami.org/ https://nami.org/

Consistent

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

Certificate validity

41
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: SJC)
Got: cf-ray: 9eff7b851c066c48-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9eff7b851c066c48-SJC
A+
DNS Records
3 A records, 17 ms lookup
PASS
3 A records, 17 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 172.67.75.37, 104.26.14.208, 104.26.15.208
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:ed0, 2606:4700:20::681a:fd0, 2606:4700:20::ac43:4b25
Info::
2 nameserver(s) configured
Got: becky.ns.cloudflare.com, sri.ns.cloudflare.com
Info::
1 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: 17 ms
Got: 17 ms
A172.67.75.37, 104.26.14.208, 104.26.15.208
AAAA2606:4700:20::681a:ed0, 2606:4700:20::681a:fd0, 2606:4700:20::ac43:4b25
CNAME
NSbecky.ns.cloudflare.com, sri.ns.cloudflare.com
MX
0 nami-org.mail.protection.outlook.com
TXT
00D36000001F14U=1TBRi0000000HAX
1password-site-verification=N7NRN7YA2RCXLD72QBIF7QB47I
2i984o158tlsgvp0j7gp0usmbp
8o0fatu86kaejigpi18vi6ej85
ZOOM_verify_fv22rFEjRe6c6VQPOUIdYw
anthropic-domain-verification-vgaz0g=05CME26PZ4cjMtRDtdsQXonMy
apple-domain-verification=bArsPWmIZZB79Mj4
ca3-01f93e1d295c473795ebdbc4079db4aa
dropbox-domain-verification=97ux7903f5x2
facebook-domain-verification=34xolbmf7kba6rjdluufhb4343093x
figma-domain-verification=b64c26a27c4bf4d235df9c4cca4e2cbf3e9eff4f1008fef1cf61b3...
google-site-verification=S37Bp_1u3LXUHaqyLi6JdH0gNG20NYjPkBqy8ai8sOw
google-site-verification=jIvHWCZT_mcqxXRwpGX_YofNqBhDJVKgj1dV9iSiohA
google-site-verification=tMkONkziDdPWuEj60XaKpe1Yvz9OAjFvkM1xMLKFrwE
mandrill_verify.XmxQIrzPVLS76-8yDjhOiw
nami-k11-newprod.azurewebsites.net
nami-k11.azurewebsites.net
namiprod.azurewebsites.net
openai-domain-verification=dv-70kwUYBcQiJZF95bqsB8q0gQ
perplexity-ai-domain-verification-mt06ar=rV9Wd9MRtcw8vJerDiDHnqxva
ppe-c8fcfec53b28efb6cc6293b56d4c951b68854545
SPF v=spf1 include:_s01096488.autospf.email -all
CAALookup not available with standard resolver
Resolved in 17 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
1 redirect(s), 85 ms total
PASS
1 redirect(s), 85 ms total
Info::
Single redirect
Got: https://nami.org → https://www.nami.org/ (301)
Info::
WWW normalization redirect

https://nami.org

36 ms · HTTP/1.1

301

https://www.nami.org/

49 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nami.org30136 msHTTP/1.1cloudflare
2https://www.nami.org/20049 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 23 URLs
PASS
robots.txt present, sitemap with 23 URLs
Info::
robots.txt is present
Got: 1738 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 23 entries
Info::
Sitemap index with 23 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1738 B Sitemaps referenced 0 User-agents *, Amazonbot, Applebot-Extended, Bytespider, ClaudeBot, CloudflareBrowserRenderingCrawler, Google-Extended, CCBot, GPTBot, meta-externalagent Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content


A+
HTTP Probe Timing
Total 34 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 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.
34 ms
Total Time Total request time from DNS lookup through full response.
34 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 4 ms TLS Handshake 11 ms Server Processing 13 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback