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
# OpenStreetMap's data is available for free in bulk from https://planet.openstreetmap.org
# For regional extracts and documentation, see https://wiki.openstreetmap.org/wiki/Planet.osm
# We encourage you to use these instead of scraping our site.
# Scraping puts a high load on our donated resources and will lead to your IP being blocked.
# Please respect our resources, and help us keep the service free and accessible for everyone.
User-agent: *
Disallow: /user/*/traces/
Disallow: /user/*/history
Allow: /user/
Disallow: /traces
Disallow: /api/
Disallow: /edit
Disallow: /changeset
Disallow: /node
Disallow: /note
Disallow: /relation
Disallow: /way
Disallow: /login
Disallow: /geocoder
Disallow: /history
Disallow: /message
Disallow: /oauth2
Disallow: /search
Disallow: /trace/
Disallow: /*lat=
Disallow: /*node=
Disallow: /*way=
Disallow: /*relation=
Host: www.openstreetmap.org
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 & Recommendations78 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records4 A records, 10 ms lookupPASS
| A | 151.101.1.55, 151.101.65.55, 151.101.129.55, 151.101.193.55 |
| AAAA | 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:400::311, 2a04:4e42:600::311 |
| CNAME | — |
| NS | daisy.ns.cloudflare.com, rajeev.ns.cloudflare.com |
| MX | 10 a.mx.openstreetmap.org |
| TXT | facebook-domain-verification=j5hix5i8r0kortfugqf2p9wx9x9by0 _globalsign-domain-verification=W0buKB5ZmL-VwwHw2oQyQImk3I1q3hSemf2qmB1hjP _globalsign-domain-verification=ps00GlW1BzY9c2_cwH_pFqRkvzZyaCVZ-3RLssRG6S SPF v=spf1 ip4:184.104.226.98 ip6:2001:470:1:b3b::2 ip4:87.252.214.98 ip6:2001:4d78:... |
| 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), 384 ms totalPASS
https://openstreetmap.org
16 ms · HTTP/1.1
https://www.openstreetmap.org/
368 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://openstreetmap.org | 301 | 16 ms | HTTP/1.1 | Varnish |
| 2 | https://www.openstreetmap.org/ | 200 | 368 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligenceopenstreetmap.org — via Gandi SAS, 21 years, 11 months oldPASS
1124 days
August 9, 2029
78 days
Issued by Let's Encrypt
21 years, 11 months
Registered August 9, 2004
Enabled
Protects against DNS spoofing
Unknown
2a04:4e42::311
Gandi SAS
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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