Skip to content
https://carnegieendowment.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 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
TLS Certificate Expiry & Recommendations
254 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

254
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
4 A records, 28 ms lookup
PASS
4 A records, 28 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 65.8.202.48, 65.8.202.54, 65.8.202.106, 65.8.202.41
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns-1308.awsdns-35.org, ns-782.awsdns-33.net
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: 28 ms
Got: 28 ms
A65.8.202.48, 65.8.202.54, 65.8.202.106, 65.8.202.41
AAAA
CNAME
NSns-1308.awsdns-35.org, ns-782.awsdns-33.net
MX
0 ceip-org.mail.protection.outlook.com
TXT
globalsign-domain-verification=9e951de685c8b2af63529821752dc106
google-site-verification=ReLwjMc51AmeoDJm8Q_J0cApiOukyapbxsbM_XmoxYM
SPF v=spf1 a:vpn.ceip.org mx include:mktomail.com include:amazonses.com include:spf....
CAALookup not available with standard resolver
Resolved in 28 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://carnegieendowment.org

https://carnegieendowment.org

11 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://carnegieendowment.org20011 msHTTP/1.1
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 93 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 93 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /admin/

Sitemap: https://carnegieendowment.org/sitemap.xml

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.carnegieendowment.org/
200https://carnegieendowment.org/

HTTP → HTTPS

301http://carnegieendowment.org/ https://carnegieendowment.org/

Consistent

A+
Domain Intelligence
carnegieendowment.org — via GoDaddy.com, LLC, 24 years, 10 months old, hosted on AWS
PASS
carnegieendowment.org — via GoDaddy.com, LLC, 24 years, 10 months old, hosted on AWS
Info::
Domain registered until Oct 16, 2028 (2 years, 6 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: AWS
Got: AS16509
Domain expiry

821 days

October 16, 2028

SSL certificate

254 days

Issued by Amazon

Domain age

24 years, 10 months

Registered October 16, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

65.8.202.41

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 October 16, 2001 (24 years, 10 months ago)
Expires October 16, 2028 (2 years, 6 months)
Last Updated June 9, 2024
Name Servers ns-1308.awsdns-35.org, ns-782.awsdns-33.net
DNSSEC Not enabled
Hosting
IP Address 65.8.202.41
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 41 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
40 ms
Total Time Total request time from DNS lookup through full response.
42 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 6 ms Content Transfer 2 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD56-P6)
Got: x-amz-cf-id: JFA-zivvxsdWh1-wokVl_MwVAz6tWXkLFzIKy7rnVQW7x6caHj33og==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: JFA-zivvxsdWh1-wokVl_MwVAz6tWXkLFzIKy7rnVQW7x6caHj33og==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback