Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations51 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records1 A records, 27 ms lookupPASS
| A | 50.116.19.161 |
| AAAA | — |
| CNAME | — |
| NS | cortney.ns.cloudflare.com, dimitris.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | MS=30879FAE6998B1D64DFF6A578BAADC9BD072313C MS=ms90557443 google-site-verification=8O5FwGq_9lvEbH_YCnzyiNNqiLNtQbwBmk-b0LG69Eg google-site-verification=Ez1DwE98RbLxbAb8RrO9ev9kPPzJ7ZsoTn1IuVv-T58 SPF v=spf1 include:_spf.google.com include:amazonses.com include:spf.mandrillapp.com... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Redirect ChainNo redirects — direct accessPASS
https://fas.org
142 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://fas.org | 200 | 142 ms | HTTP/1.1 | nginx |
A+Crawlabilityrobots.txt present, sitemap with 24 URLsPASS
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:
Sitemap: https://fas.org/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
- https://fas.org/post-sitemap.xml
- https://fas.org/page-sitemap.xml
- https://fas.org/issues-sitemap.xml
- https://fas.org/publications-sitemap.xml
- https://fas.org/publications-sitemap2.xm...
- https://fas.org/publications-sitemap3.xm...
- https://fas.org/publications-sitemap4.xm...
- https://fas.org/publications-sitemap5.xm...
- https://fas.org/publications-sitemap6.xm...
- https://fas.org/talent-hub-sitemap.xml
- https://fas.org/initiatives-sitemap.xml
- https://fas.org/accelerators-sitemap.xml
- https://fas.org/careers-sitemap.xml
- https://fas.org/staff-sitemap.xml
- https://fas.org/staff-sitemap2.xml
- https://fas.org/events-sitemap.xml
- https://fas.org/category-sitemap.xml
- https://fas.org/post_tag-sitemap.xml
- https://fas.org/event_category-sitemap.x...
- https://fas.org/publication-type-sitemap...
- https://fas.org/publication-term-sitemap...
- https://fas.org/staff-category-sitemap.x...
- https://fas.org/career-category-sitemap....
- https://fas.org/author-sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefas.org — via GoDaddy.com, LLC, 31 years, 6 months old, hosted on AkamaiPASS
616 days
March 24, 2028
51 days
Issued by Let's Encrypt
31 years, 6 months
Registered March 23, 1995
Not enabled
Protects against DNS spoofing
Akamai
ASN AS63949
50.116.19.161
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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