Skip to content
https://aaos.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1052 ms total
REVIEW
1 redirect(s), 1052 ms total
Info::
Single redirect
Got: https://aaos.org → https://www.aaos.org/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1052 ms total
Got: 1052 ms

https://aaos.org

385 ms · HTTP/1.1

301

https://www.aaos.org/

667 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aaos.org301385 msHTTP/1.1
2https://www.aaos.org/200667 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.aaos.org/
200https://aaos.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://aaos.org/ https://aaos.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

131
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
A+
DNS Records
1 A records, 53 ms lookup
PASS
1 A records, 53 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 172.171.25.79
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: pdns77.ultradns.org, pdns77.ultradns.biz, pdns77.ultradns.net, pdns77.ultradns.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: 53 ms
Got: 53 ms
A172.171.25.79
AAAA
CNAME
NSpdns77.ultradns.org, pdns77.ultradns.biz, pdns77.ultradns.net, pdns77.ultradns.com
MX
10 us-smtp-inbound-1.mimecast.com
10 us-smtp-inbound-2.mimecast.com
TXT
aaos-app-prod-epi01.azurewebsites.net
ckcwlk137r3yflnrdcxq0158hk85rxjz
atlassian-domain-verification=wbf1x9dfLXyZJIfwl8mC+3JONdGjc1zbKpYCUQmAC2FLhlv/0I...
google-site-verification=uUgOipwYJpqgIFu5-AIcbqns_1UvmG75Eupg_XaaNJ8
anthropic-domain-verification-be05b9=uL1xpplzLMutxwAnYUVw8ISPN
u9qaldq2mql9d1rt9jmjehkecg
vj0013j1qf909m7s1276lfmjkg
SPF v=spf1 redirect=ciqi3fw7._spf._d.mim.ec
google-site-verification=tiQ8Qv39ziNUZMS7JHZ68iYfUw85TiMdBvYyPUIJwfo
CAALookup not available with standard resolver
Resolved in 53 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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+
Crawlability
robots.txt present, sitemap with 2935 URLs
PASS
robots.txt present, sitemap with 2935 URLs
Info::
robots.txt is present
Got: 100 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2935 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 100 B Sitemaps referenced 2 User-agents Blocking No — crawling allowed

Sitemap: http://www.aaos.org/standard_sitemap.xml

Sitemap: http://www.aaos.org/mobile_sitemap.xml
A+
Domain Intelligence
aaos.org — via Network Solutions, LLC, 31 years, 5 months old, hosted on Microsoft Azure
PASS
aaos.org — via Network Solutions, LLC, 31 years, 5 months old, hosted on Microsoft Azure
Info::
Domain registered until Apr 11, 2030 (4 years 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.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

1397 days

April 11, 2030

SSL certificate

131 days

Issued by GoDaddy.com, Inc.

Domain age

31 years, 5 months

Registered April 10, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

172.171.25.79

Registrar

Network Solutions, LLC

Unlocked 4 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 April 10, 1995 (31 years, 5 months ago)
Expires April 11, 2030 (4 years)
Last Updated April 11, 2020
Name Servers pdns77.ultradns.org, pdns77.ultradns.biz, pdns77.ultradns.com, pdns77.ultradns.net
DNSSEC Not enabled
Hosting
IP Address 172.171.25.79
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
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 433 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
124 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
125 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
433 ms
Total Time Total request time from DNS lookup through full response.
433 ms

Connection waterfall

DNS Lookup 60 ms TCP Connect 124 ms TLS Handshake 125 ms Server Processing 124 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