Skip to content
https://asha.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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.asha.org/
200https://asha.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://asha.org/ https://www.asha.org/

Consistent

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

Certificate validity

52
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: SIN)
Got: cf-ray: 9f08170e5e683e35-SIN
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f08170e5e683e35-SIN
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.163.69, 104.20.23.26
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:171a, 2606:4700:10::ac42:a345
Info::
2 nameserver(s) configured
Got: dorthy.ns.cloudflare.com, evan.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: 9 ms
Got: 9 ms
A172.66.163.69, 104.20.23.26
AAAA2606:4700:10::6814:171a, 2606:4700:10::ac42:a345
CNAME
NSdorthy.ns.cloudflare.com, evan.ns.cloudflare.com
MX
0 asha-org.mail.protection.outlook.com
TXT
4FVgFOEmxHZILLLRLbQNLFe96TM4Nai7nxpjCJZjfky6mQ/Jv0H1pdqQCX90AztbCe9VX8O4pbeX/n7N...
8vc8/iQSviGYt8mXi5zT12RpyAE2CpKkfbRfkwDVYxfzxqPgkmoYSY+Cmwi5f7IW54ursaMbrH2ECf1s...
asha.org: zCB76BiZvsYB6f5rivyMQYmcLt+bXlmkgPeMAfXog9RBKjaJ0KlZyW4zVJdZYacdSeATNT...
atlassian-domain-verification=6WQScZa17PFZS8GajxDQxA60aeCrSNsW8r8hfWdHlHEazOXmLo...
cisco-ci-domain-verification=10cd39b033d5981b9b9900f4fc1ebfd78294df48635360890da...
docusign=8013a172-5402-4612-b972-d5454fa78ac0
docusign=96ef7899-ccdc-49e1-bc14-7d921412fa28
facebook-domain-verification=qsybde90ry4olkxzv1ifwg53behmk0
google-site-verification=jW57WOnz9vDVQV80gXhMc9hC6JH5GISOOlstwP3-M4Q
google-site-verification=owendpSVf57sql36XbkDx50yjl5h44YfqwRBa-EYPSc
SPF v=spf1 ip4:54.208.161.176 ip4:54.208.181.200 ip4:54.208.202.83 ip4:54.209.164.22...
CAALookup not available with standard resolver
Resolved in 9 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), 313 ms total
PASS
1 redirect(s), 313 ms total
Info::
Single redirect
Got: https://asha.org → https://www.asha.org/ (301)
Info::
WWW normalization redirect

https://asha.org

31 ms · HTTP/1.1

301

https://www.asha.org/

282 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://asha.org30131 msHTTP/1.1cloudflare
2https://www.asha.org/200282 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::6814:171a, 2606:4700:10::ac42:a345
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::6814:171a, 2606:4700:10::ac42:a345 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 4968 URLs
PASS
robots.txt present, sitemap with 4968 URLs
Info::
robots.txt is present
Got: 1071 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4968 entries
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 1071 B Sitemaps referenced 0 User-agents Yandex, Baiduspider-video, ia_archiver, *, AhrefsBot, ichiro, NaverBot, sogou spider, YoudaoBot, scrapy, wotbox, moget, Baiduspider, Baiduspider-image, vegebot, bingbot, facebookexternalhit, RavenCrawler, Yeti, seznambot, SputnikBot, kinshoobot, SemrushBot Blocking No — crawling allowed
User-agent: *

Disallow: /EPiServer/CMS/

Disallow: /Util/

Disallow: /Test-Pages/

Disallow: /eweb/ashalogin.aspx*


Disallow: /workarea

Disallow: /widgets

Disallow: /uploadedimages

Disallow: /*.axd$

Disallow: /PRPPrintTemplate.aspx*


User-agent: facebookexternalhit

Disallow: /uploadedfiles

Disallow: /uploadedimages




User-agent: AhrefsBot

Disallow: /


User-agent: RavenCrawler

Disallow: /


User-agent: Yandex

Disallow: /


User-agent: moget

User-agent: ichiro

Disallow: /


User-agent: NaverBot

User-agent: Yeti

Disallow: /


User-agent: Baiduspider

User-agent: Baiduspider-video

User-agent: Baiduspider-image

Disallow: /


User-agent: sogou spider

Disallow: /


User-agent: YoudaoBot

Disallow: /


user-agent: scrapy

Disallow: /


user-agent: seznambot

Disallow: /


user-agent: SputnikBot

Disallow: /


user-agent: kinshoobot

Disallow: /


user-agent: vegebot

Disallow: /


User-agent: wotbox

Disallow: /


User-agent: bingbot

Disallow: 


User-agent: ia_archiver

Disallow: /


User-agent: SemrushBot

Disallow: /
A+
Domain Intelligence
asha.org — via Network Solutions, LLC, 32 years, 4 months old
PASS
asha.org — via Network Solutions, LLC, 32 years, 4 months old
Info::
Domain registered until May 13, 2034 (8 years, 2 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: Network Solutions, 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

2888 days

May 13, 2034

SSL certificate

52 days

Issued by Google Trust Services

Domain age

32 years, 4 months

Registered May 12, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::6814:171a

Registrar

Network Solutions, 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 Network Solutions, LLC
Created May 12, 1994 (32 years, 4 months ago)
Expires May 13, 2034 (8 years, 2 months)
Last Updated May 18, 2024
Name Servers dorthy.ns.cloudflare.com, evan.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::6814:171a
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 17 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