Skip to content
https://ushmm.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
4 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

200https://www.ushmm.org/
200https://ushmm.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

403http://ushmm.org/

HTTP version does not redirect to HTTPS

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.

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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

320
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, 43 ms lookup
PASS
1 A records, 43 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 50.144.202.30
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: edns2.ultradns.org, edns2.ultradns.biz, edns2.ultradns.com, edns2.ultradns.net
Info::
5 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: 43 ms
Got: 43 ms
A50.144.202.30
AAAA
CNAME
NSedns2.ultradns.org, edns2.ultradns.biz, edns2.ultradns.com, edns2.ultradns.net
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
miro-verification=2a157e30e68d6f58a7d3a176f61d0aabc39b78c0
jamf-site-verification=OgBGg6Pxte-TXigqnqCDgw
b0f4b142e971e905afa50c9548ea93b0e4508f4fa69bb2260a19e45c38cdd52e
ZOOM_verify_kInvqjVMThmIpy2u0kHbsg
google-site-verification=j_QUAWQ-H1VK9HdOpJMD_goK-KMfQquKVSw-QfznUgs
atlassian-domain-verification=TKLaQ4jEIp1x/aA547RS4WHick3F6wkaz3RoWUauzx72eicDB3...
77b70c45-f973-44d0-8083-e40c785a649b
atlassian-domain-verification=gk87bBYOaX22kk9MFpfKhQuZ5w7crXifbQYFxkSWvmbQkcbrSF...
google-site-verification=F_Ofx_lN9LSTDweF91-NEeXRCmAJPdUHki84NaULDyM
MS=ms15993877
apple-domain-verification=nROvn3WuybUjKrLY
SPF v=spf1 ip4:50.144.202.0/25 ip4:44.198.253.9/32 include:_spf.google.com include:m...
google-site-verification=sFYEFQazLdFm677ha3TAKLfM9QeSnKnF0dM-MhaqFYw
docusign=0d1f8006-64cb-4f33-98ab-b069ba4d4ca7
adobe-idp-site-verification=e4ebeb175a25ee6383dcc347c6fc9feb98f86ff1c117ea498561...
docusign=b92e2ed4-f04e-43ba-8a3d-a56863e4de14
0e51ff7a-409e-458b-994f-04942c0aaf5f
CAALookup not available with standard resolver
Resolved in 43 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
0 redirect(s), 389 ms total
PASS
0 redirect(s), 389 ms total

https://ushmm.org

389 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ushmm.org403389 msHTTP/1.1nginx
A+
Domain Intelligence
ushmm.org — via Network Solutions, LLC, 32 years, 11 months old, hosted on UNITED-STATES-HOLOCAUST-MEMORIAL-MUSEUM - United States Holocaust Memorial Museum, US
PASS
ushmm.org — via Network Solutions, LLC, 32 years, 11 months old, hosted on UNITED-STATES-HOLOCAUST-MEMORIAL-MUSEUM - United States Holocaust Memorial Museum, US
Info::
Domain registered until Oct 27, 2026 (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: 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: UNITED-STATES-HOLOCAUST-MEMORIAL-MUSEUM - United States Holocaust Memorial Museum, US
Got: AS33738
Domain expiry

135 days

October 27, 2026

SSL certificate

320 days

Issued by Entrust Limited

Domain age

32 years, 11 months

Registered October 28, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

UNITED-STATES-HOLOCAUST-MEMORIAL-MUSEUM - United States Holocaust Memorial Museum, US

ASN AS33738

50.144.202.30

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 October 28, 1993 (32 years, 11 months ago)
Expires October 27, 2026 (6 months)
Last Updated September 2, 2021
Name Servers edns2.ultradns.org, edns2.ultradns.biz, edns2.ultradns.com, edns2.ultradns.net
DNSSEC Not enabled
Hosting
IP Address 50.144.202.30
ASN AS33738 (UNITED-STATES-HOLOCAUST-MEMORIAL-MUSEUM - United States Holocaust Memorial Museum, US)
Provider UNITED-STATES-HOLOCAUST-MEMORIAL-MUSEUM - United States Holocaust Memorial Museum, US
Data source: rdap (0.6s)

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 424 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
128 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
134 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
425 ms
Total Time Total request time from DNS lookup through full response.
425 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 128 ms TLS Handshake 134 ms Server Processing 127 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