Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# see http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
#
# to ban all spiders from the entire site uncomment the next two lines:
# user-agent: *
# disallow: /
user-agent: *
disallow: /dist/robots.*.js
disallow: /assets/robots-*.js
disallow: /calendar/events/9322
disallow: /calendar/programs/46
disallow: /calendar/programs/50
disallow: /calendar/programs/9
disallow: /calendar/exhibitions/3223
disallow: /collection/browse_results.php
disallow: /collection/object.php
disallow: /collection/artist.php
disallow: /collection/theme.php
disallow: /collection_lb/browse_results.php
disallow: /collection_ge/browse_results.php
disallow: /collection/search.php
disallow: /visit/calendar/search
disallow: /visit/calendar/filters
disallow: /visit/calendar/films?day*
disallow: /screens/*
disallow: /visit/wifi/
disallow: /cdn-cgi/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations57 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 79 ms lookupPASS
| A | 104.18.9.51, 104.18.8.51 |
| AAAA | 2606:4700::6812:833, 2606:4700::6812:933 |
| CNAME | — |
| NS | logan.ns.cloudflare.com, wren.ns.cloudflare.com |
| MX | 0 mxa-004c0e03.gslb.pphosted.com 0 mxb-004c0e03.gslb.pphosted.com |
| TXT | dptqjki8g3tpucjbno6bv0r3ed jamf-site-verification=6kUWqIVkyYyYgf0RoJ_ZHQ SPF v=spf1 include:_spf.google.com ip4:63.117.124.0/24 ip4:65.211.53.131 ip4:38.125.... apple-domain-verification=30ovqro8hjqtAhgr 6c7i0ouo1f4lfseov2dnbc1di4 adobe-idp-site-verification=0c9cf8b4135f0a8731823b237d8cf4a91045693c783f74dbce5f... google-site-verification=Pr3kjMN9vtOp3O8BqAWWYoelYopZAUO7Q8eqYosiMTI asv=5af33c11b29472a1d1f53d055ae36eb5 google-site-verification=3vrESLJUNQb4JqQa8uIUtVm0gkEsm5oafDbFFb-Gmfg have-i-been-pwned-verification=3bd956232b1c0dad85b7b5242f3720df google-site-verification=Y-uTmVZnxgZVfkpYVvi7X3qlAYSc1xdliEpLwZoIFao facebook-domain-verification=96ykiggrug8zd9zhq3ejj0o2xjaa5a anthropic-domain-verification-5jmb3h=HkL8hTUNs7yxLr4I6dZEQ6iau MS=9B2FE3DB81DB00D53D1BFA0F1D9897DCB7619E42 goodnotes-verification=94d9f771-8767-4f8d-a3c3-4c17bf561900 |
| CAA | Lookup not available with standard resolver |
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.
ARedirect Chain1 redirect(s), 796 ms totalPASS
https://moma.org
66 ms · HTTP/1.1
https://www.moma.org/
731 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://moma.org | 301 | 66 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.moma.org/ | 200 | 731 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Domain Intelligencemoma.org — via Cloudflare, Inc., 31 years, 5 months oldPASS
285 days
April 27, 2027
57 days
Issued by Google Trust Services
31 years, 5 months
Registered April 26, 1995
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6812:833
Cloudflare, Inc.
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