Skip to content
https://guggenheim.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
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 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.guggenheim.org/
200https://guggenheim.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://guggenheim.org/ → https://www.guggenheim.org/

Consistent

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

Certificate validity

40
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, 51 ms lookup
PASS
1 A records, 51 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.185.0.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:12a:8001::2, 2620:12a:8000::2
Info::
4 nameserver(s) configured
Got: ns-1675.awsdns-17.co.uk, ns-265.awsdns-33.com, ns-633.awsdns-15.net, ns-1422.awsdns-49.org
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: 51 ms
Got: 51 ms
A23.185.0.2
AAAA2620:12a:8001::2, 2620:12a:8000::2
CNAME—
NSns-1675.awsdns-17.co.uk, ns-265.awsdns-33.com, ns-633.awsdns-15.net, ns-1422.awsdns-49.org
MX
0 guggenheim-org.mail.protection.outlook.com
TXT
MS=ms49509401
20o63MoMxDt0a5YJHrUa0AQiOGjvJKfDQP1HWh+EjurqD+18XBpNZFqJQPsKCtoitBz3wTV8saAqmbai...
google-site-verification=PChbk09jG4UFx4ofiuSkdtl0IcsFXMSdHrUA_l4Jrxcfacebook-dom...
apple-domain-verification=PyTAsWET6lDJKwhS
SPF v=spf1 ip4:64.124.176.69 ip4:172.254.222.85 ip4:192.168.1.154 ip4:166.78.121.171...
google-site-verification=OO1G_LqrsK0-dxxk4BT9I2s0j8WjxYqIvwjsVKZP_b0
facebook-domain-verification=9o2ckl3mv1pvzct9q868tqczy3limd
CAALookup not available with standard resolver
Resolved in 51 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
Redirect Chain
1 redirect(s), 191 ms total
PASS
1 redirect(s), 191 ms total
Info::
Single redirect
Got: https://guggenheim.org → https://www.guggenheim.org/ (301)
Info::
WWW normalization redirect

https://guggenheim.org

7 ms · HTTP/1.1

301

https://www.guggenheim.org/

185 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://guggenheim.org3017 msHTTP/1.1Pantheon
2https://www.guggenheim.org/200185 msHTTP/1.1nginx

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 2620:12a:8001::2, 2620:12a:8000::2
Got: 1 ms connect
IPv6 Ready
AAAA Records 2620:12a:8001::2, 2620:12a:8000::2 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 304 URLs
PASS
robots.txt present, sitemap with 304 URLs
Info::
robots.txt is present
Got: 128 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 304 entries
Info::
Sitemap index with 304 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 128 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-login.php
# Sitemap archive
Sitemap: https://www.guggenheim.org/wp-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 304 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
guggenheim.org — via Gandi SAS, 31 years, 5 months old
PASS
guggenheim.org — via Gandi SAS, 31 years, 5 months old
Info::
Domain registered until May 5, 2027 (1 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: Gandi SAS
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

297 days

May 5, 2027

SSL certificate

40 days

Issued by Let's Encrypt

Domain age

31 years, 5 months

Registered May 4, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8001::2

Registrar

Gandi SAS

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 Gandi SAS
Created May 4, 1995 (31 years, 5 months ago)
Expires May 5, 2027 (1 years)
Last Updated March 11, 2026
Name Servers ns-1422.awsdns-49.org, ns-1675.awsdns-17.co.uk, ns-265.awsdns-33.com, ns-633.awsdns-15.net
DNSSEC Not enabled
Hosting
IP Address 2620:12a:8001::2
Data source: rdap (0.3s)

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 202 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
196 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.
203 ms
Total Time Total request time from DNS lookup through full response.
203 ms

Connection waterfall

DNS Lookup 196 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 3 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350028-TOJ
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350028-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback