Skip to content
https://komoot.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
Redirect Chain
1 redirect(s), 3633 ms total
REVIEW
1 redirect(s), 3633 ms total
Info::
Single redirect
Got: https://komoot.com → https://www.komoot.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 3633 ms total
Got: 3633 ms

https://komoot.com

53 ms · HTTP/1.1

301

https://www.komoot.com/

3580 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://komoot.com30153 msHTTP/1.1CloudFront
2https://www.komoot.com/2003580 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1039 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1039 B Sitemaps referenced 0 User-agents AwarioRssBot, AwarioSmartBot, CCBot, *, FAST-WebCrawler, rogerbot, dotbot, DataForSeoBot, MJ12bot, ZoomBot, FAST Enterprise Crawler, barkrowler, BLEXBot Blocking No — crawling allowed
User-agent: FAST Enterprise Crawler
User-agent: FAST-WebCrawler
User-agent: barkrowler
User-agent: rogerbot
User-agent: dotbot
User-agent: DataForSeoBot
User-agent: BLEXBot
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: MJ12bot
User-Agent: ZoomBot
User-agent: CCBot
Disallow: /

User-agent: *
Disallow: /_democase-test-area/
Disallow: /_fb-apps/
Disallow: /_mail/
Disallow: /_newsletter/
Disallow: /_partner/
Disallow: /_plugin-test-area/
Disallow: /tiles
Disallow: /account
Disallow: /api
Disallow: /contact/goodbye.html
Disallow: /error
Disallow: /external/importer.html
Disallow: /privacy
Disallow: /tools
Disallow: /product/buy
Disallow: /service
Disallow: /terms-of-service
Disallow: /static
Disallow: /5years
Disallow: /g/
Disallow: /redeem
Disallow: /campaign
Disallow: /dpp
Disallow: /product/promotion
Disallow: /user/kommot
Disallow: /user/komot
Disallow: /user/koomot
Disallow: /user/kommoot
Disallow: /plan?*similar=*
Disallow: /projects/vef
Disallow: /projects/volksentscheid-fahrrad
Disallow: /projects/radg

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.komoot.com/
200https://komoot.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://komoot.com/ https://komoot.com/

Consistent

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

Certificate validity

299
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
B
CDN & Delivery
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG52-P4)
Got: x-amz-cf-id: pI7orgjRAM1Ly6l0zxFwVBB7ficmwo8WA6wc6ScQQg8bjcDb1seF_Q==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: pI7orgjRAM1Ly6l0zxFwVBB7ficmwo8WA6wc6ScQQg8bjcDb1seF_Q==
A+
DNS Records
4 A records, 47 ms lookup
PASS
4 A records, 47 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.155.129.31, 18.155.129.23, 18.155.129.81, 18.155.129.104
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:244f:1a00:a:ee06:4800:93a1, 2600:9000:244f:9200:a:ee06:4800:93a1, 2600:9000:244f:6400:a:ee06:4800:93a1, 2600:9000:244f:8600:a:ee06:4800:93a1, 2600:9000:244f:4000:a:ee06:4800:93a1, 2600:9000:244f:9800:a:ee06:4800:93a1, 2600:9000:244f:1000:a:ee06:4800:93a1, 2600:9000:244f:f200:a:ee06:4800:93a1
Info::
4 nameserver(s) configured
Got: ns-1965.awsdns-53.co.uk, ns-1115.awsdns-11.org, ns-240.awsdns-30.com, ns-655.awsdns-17.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: 47 ms
Got: 47 ms
A18.155.129.31, 18.155.129.23, 18.155.129.81, 18.155.129.104
AAAA2600:9000:244f:1a00:a:ee06:4800:93a1, 2600:9000:244f:9200:a:ee06:4800:93a1, 2600:9000:244f:6400:a:ee06:4800:93a1, 2600:9000:244f:8600:a:ee06:4800:93a1, 2600:9000:244f:4000:a:ee06:4800:93a1, 2600:9000:244f:9800:a:ee06:4800:93a1, 2600:9000:244f:1000:a:ee06:4800:93a1, 2600:9000:244f:f200:a:ee06:4800:93a1
CNAME
NSns-1965.awsdns-53.co.uk, ns-1115.awsdns-11.org, ns-240.awsdns-30.com, ns-655.awsdns-17.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
google-site-verification=Y9ZR8ANjvjRzs_8vhMpXRanScUiuecLyOxPulGfZ3LI
google-site-verification=hmWcpPRS4ExamwT139hRszWl6Sf3XxFLDlfmodN1tJI
xzd3ayqm8x
atlassian-domain-verification=eVR1Hb2w1knsN0ID4jSivQgWon98eRB3itNQDubmSu1y07o71G...
google-site-verification=eLemtoDi6GEzuOeBWiapWxzsT3V5Ey0_epI06mBfi28
google-site-verification=MSH1W04PFZQxG4l2JCqK7W8Ct2Q1-gQ0JKOzaqSPQp4
google-site-verification=2tQx73RWNjw8zryIE9KN3oxSyKxHekofDXAM67xuW9I
google-site-verification=OfFb7GXbdirIzECIlz9RmW5MHqSU8H3Wkc2IXjKvVYk
h1-domain-verification=DEqVF5o4dSbrpHmV1AykFw73jcn4t8fhhhso9JcBiTyTn3xT
ZOOM_verify_IUlYjMAzS6qm7P8JuwKdvg
SPF v=spf1 include:amazonses.com include:_spf.google.com include:mail.zendesk.com ~a...
CAALookup not available with standard resolver
Resolved in 47 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+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2600:9000:244f:1a00:a:ee06:4800:93a1, 2600:9000:244f:9200:a:ee06:4800:93a1, 2600:9000:244f:6400:a:ee06:4800:93a1, 2600:9000:244f:8600:a:ee06:4800:93a1, 2600:9000:244f:4000:a:ee06:4800:93a1, 2600:9000:244f:9800:a:ee06:4800:93a1, 2600:9000:244f:1000:a:ee06:4800:93a1, 2600:9000:244f:f200:a:ee06:4800:93a1
Got: 16 ms connect
IPv6 Ready
AAAA Records 2600:9000:244f:1a00:a:ee06:4800:93a1, 2600:9000:244f:9200:a:ee06:4800:93a1, 2600:9000:244f:6400:a:ee06:4800:93a1, 2600:9000:244f:8600:a:ee06:4800:93a1, 2600:9000:244f:4000:a:ee06:4800:93a1, 2600:9000:244f:9800:a:ee06:4800:93a1, 2600:9000:244f:1000:a:ee06:4800:93a1, 2600:9000:244f:f200:a:ee06:4800:93a1 Connection Reachable (16 ms)
A+
Domain Intelligence
komoot.com — via Amazon Registrar, Inc., 17 years, 8 months old
PASS
komoot.com — via Amazon Registrar, Inc., 17 years, 8 months old
Info::
Domain registered until Oct 30, 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: Amazon Registrar, Inc.
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

105 days

October 30, 2026

SSL certificate

299 days

Issued by Amazon

Domain age

17 years, 8 months

Registered October 30, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:244f:9800:a:ee06:4800:93a1

Registrar

Amazon Registrar, Inc.

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 Amazon Registrar, Inc.
Created October 30, 2008 (17 years, 8 months ago)
Expires October 30, 2026 (6 months)
Last Updated September 25, 2025
Name Servers ns-1115.awsdns-11.org, ns-1965.awsdns-53.co.uk, ns-240.awsdns-30.com, ns-655.awsdns-17.net
DNSSEC Not enabled
Hosting
IP Address 2600:9000:244f:9800:a:ee06:4800:93a1
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 47 ms TCP Connect 16 ms TLS Handshake 18 ms Server Processing 18 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