Skip to content
https://aei.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
4 PASS 5 REVIEW
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

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1738 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 Google-Extended, meta-externalagent, *, Bytespider, CCBot, CloudflareBrowserRenderingCrawler, GPTBot, Amazonbot, Applebot-Extended, ClaudeBot 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


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::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.aei.org/
200https://aei.org/

HTTP → HTTPS

403http://aei.org/

HTTP version does not redirect to HTTPS

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

Certificate validity

93
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: 9f075c40ab40bb76-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f075c40ab40bb76-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: 172.66.139.211, 172.66.135.23
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: kip.ns.cloudflare.com, erin.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
A172.66.139.211, 172.66.135.23
AAAA
CNAME
NSkip.ns.cloudflare.com, erin.ns.cloudflare.com
MX
10 d357194a.ess.barracudanetworks.com
20 d357194b.ess.barracudanetworks.com
TXT
duo_sso_verification=dLmlmfzVPxn0DEHpzgNmn6emTeRFTN0PvYt8wGFM0Sb19PiTBKjhJYw37pC...
ncp36kvbwsy1gn972rzn43djtwsqjmlm
MS=1343791E090D063145EEE7DFF4491F9990C5E8A3
google-site-verification=vcdgO-aF28_9vvEHbOtlJ6Qzbb5EK1XH0pi-E_sEQ-c
9ms4hppqbp547g13fkj6l7ynmhqgk5b4
facebook-domain-verification=1jpohvtdzij2lviz30i8gi8azi4kmc
MS=ms69630075
google-site-verification=1bNUTi7S6r0YRQLZCvNgcBi0xHOn8O8DV98JZIFO9Dc
asv=6abaeea05cf47533924bfc6357618c68
MS=ms71212688
SPF v=spf1 include:spf1.formassembly.com include:_spf.salesforce.com include:_spf.ml...
include:45454203.spf02.hubspotemail.net
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), 68 ms total
PASS
0 redirect(s), 68 ms total

https://aei.org

68 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aei.org40368 msHTTP/1.1cloudflare
A+
Domain Intelligence
aei.org — via GoDaddy.com, LLC, 31 years old, hosted on Cloudflare
PASS
aei.org — via GoDaddy.com, LLC, 31 years old, hosted on Cloudflare
Info::
Domain registered until Sep 27, 2030 (4 years, 5 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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

1533 days

September 27, 2030

SSL certificate

93 days

Issued by DigiCert Inc

Domain age

31 years

Registered September 28, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

172.66.135.23

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 September 28, 1995 (31 years ago)
Expires September 27, 2030 (4 years, 5 months)
Last Updated November 11, 2025
Name Servers erin.ns.cloudflare.com, kip.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 172.66.135.23
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.5s)

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 104 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.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
104 ms
Total Time Total request time from DNS lookup through full response.
104 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 26 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