Security report for citymapper.com

Name: Dark-web exposure summary for citymapper.com
Creator: OffSeq Breach

Citymapper Limited · Transportation · United Kingdom

High risk. 20 critical or high findings in Network security, Security headers and 3 other checks.

Security score

47/100

Risk levelHigh

0–100, higher is better. How it is calculated

Citymapper Limited operates a leading urban mobility platform offering a comprehensive transport app available on iPhone, Android, and web. The service integrates multiple transport modes including public transit, cycle hire, ferries, and on-demand cabs, targeting urban commuters seeking efficient multi-modal journey planning. The company is well-established with a domain age of over 19 years and a strong market presence in transportation technology. Technically, the website employs modern web technologies, including JavaScript, Typekit fonts, and a privacy SDK, with good mobile optimization and moderate performance. Security posture is solid with HTTPS and domain transfer protections, though DNSSEC is not enabled and security headers are not explicitly detected. Privacy compliance is basic with no explicit privacy or cookie policies found in the provided content. Overall, the site is professional, trustworthy, and safe for general audiences.

Scanned

NIS2 and GDPR posture

GDPR outside view: 73/ 100 · Medium
Checks completed: 7of 7

NIS2 Art. 21(2)

(a) Risk analysis and security policies: Not visible from outside
(b) Incident handling: One indicator
(c) Business continuity, backups and crisis management: Not visible from outside
(d) Supply chain security: Not visible from outside
(e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
(f) Assessing the effectiveness of security measures: Not visible from outside
(g) Cyber hygiene and security training: Not visible from outside
(h) Cryptography and encryption: Partly checked
(i) HR security, access control and asset management: One indicator
(j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

20 findings rated critical or high. Fix these first.

Network security
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
- Critical
  Critical Service Exposed: Telnet
  Port 23 (Telnet) is publicly accessible - Telnet - Unencrypted remote access
  What to do: Immediately restrict access to Telnet using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: SMB
  Port 445 (SMB) is publicly accessible - SMB - Windows file sharing, high risk
  What to do: Immediately restrict access to SMB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MSSQL
  Port 1433 (MSSQL) is publicly accessible - MSSQL - Database server
  What to do: Immediately restrict access to MSSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Oracle
  Port 1521 (Oracle) is publicly accessible - Oracle - Database server
  What to do: Immediately restrict access to Oracle using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MySQL
  Port 3306 (MySQL) is publicly accessible - MySQL - Database server
  What to do: Immediately restrict access to MySQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: RDP
  Port 3389 (RDP) is publicly accessible - RDP - Remote Desktop, prime ransomware target
  What to do: Immediately restrict access to RDP using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: PostgreSQL
  Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server
  What to do: Immediately restrict access to PostgreSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Redis
  Port 6379 (Redis) is publicly accessible - Redis - In-memory database
  What to do: Immediately restrict access to Redis using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MongoDB
  Port 27017 (MongoDB) is publicly accessible - MongoDB - NoSQL database
  What to do: Immediately restrict access to MongoDB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: FTP
  Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
  What to do: Consider restricting access to FTP or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: RPC
  Port 135 (RPC) is publicly accessible - RPC - Windows RPC endpoint
  What to do: Consider restricting access to RPC or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: NetBIOS
  Port 139 (NetBIOS) is publicly accessible - NetBIOS - Windows file sharing
  What to do: Consider restricting access to NetBIOS or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: Elasticsearch
  Port 9200 (Elasticsearch) is publicly accessible - Elasticsearch - Search engine
  What to do: Consider restricting access to Elasticsearch or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
Security headers
Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.
- High
  Missing Strict-Transport-Security header
  Forces HTTPS connections
  What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"
  References
  - CWE-319
  - OWASP A04:2025
  - ASVS V3.4.1
  - RFC 6797 §6.1.1
  - Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: hsts_min_age 63072000
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
  - NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- High
  Missing X-Frame-Options header
  Prevents clickjacking attacks
  What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"
  References
  - CWE-1021
  - OWASP A06:2025
  - CAPEC-103
  - ASVS V3.4.6
  - OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
  - RFC 7034
- High
  Missing Content-Security-Policy header
  Controls resources the browser is allowed to load
  What to do: Implement a Content-Security-Policy appropriate for your application
  References
  - ASVS V3.4.3
  - OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- High
  No Cookie Consent Banner found
  GDPR requires explicit consent for non-essential cookies
  What to do: Implement a cookie consent banner that appears on first visit
  References
  - GDPR Art. 7
  - ePrivacy Art. 5(3)
  - NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
SSL/TLS
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
- High
  Weak Protocols Supported
  Server supports weak protocols: TLSv1.1
  What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions
  References
  - CWE-327
  - OWASP A04:2025
  - ASVS V12.1.1
  - RFC 8996
  - RFC 7568
  - Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: tls_versions TLSv1.2, TLSv1.3
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
  - NIST SC-8(1): NIST SP 800-53 Rev. 5 SC-8(1): Cryptographic Protection
- High
  Weak SSL Key Length
  SSL certificate uses 256-bit key, which is considered weak
  What to do: Use at least 2048-bit RSA or 256-bit ECC key
  References
  - CWE-326
  - OWASP A04:2025
  - Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
  - NIST SC-13: NIST SP 800-53 Rev. 5 SC-13: Cryptographic Protection
DNS health
DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.
- High
  Weak SPF Policy
  SPF record has permissive policy allowing any server to send email
  What to do: Use -all or ~all qualifier for better email security

Need hands-on remediation? Email guard@offseq.com

Keep watching citymapper.com

This scan found 38 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

TLS certificates and expiry
DNS records
SPF, DKIM and DMARC
Security headers
GDPR and NIS2 posture
Exposed services
Third-party trackers
Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

The complete analysis as a PDF you can cite
Email delivery with an unlock code
Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS: 57
Security headers: 15
Email security: 70
DNS health: 65
Network security: 0
GDPR outside view: 73
Average: 47

Not counted

NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

The certificate is not trusted by browsers
The website is not served over HTTPS
A database, remote desktop, file-sharing or Telnet service is reachable from the internet · found on this site
The page loads a script from a compromised source
The domain registration has expired
SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

Critical0–25
High26–49
Medium50–75
Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention citymapper.com, from OffSeq Breach.

Total records: 359
Employees: 0
Customers: 314
Third parties: 45
Weak passwords: 25%

9 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for citymapper.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach Monitor on Breach

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Citymapper is positioned as an essential player in the transportation sector, providing a multi-modal transit app that aggregates data from various public and private transport providers. Its business model revolves around offering free routing and real-time transit information, supplemented by partnerships with ride-hailing and micro-mobility providers. The company targets urban populations in multiple cities, leveraging integrations with recognized transport brands and app stores to maintain competitive advantage. Growth indicators include extensive region and brand data embedded in the site, and a consistent brand presence. No parent or subsidiary companies were identified in the provided data.

Security posture

The security maturity level is moderate to good. The domain is secured with HTTPS and clientTransferProhibited status, reducing risk of hijacking. However, DNSSEC is not enabled, which could be improved to protect DNS integrity. No explicit security policies, incident response contacts, or vulnerability disclosure programs are published, indicating gaps in transparency and readiness. The use of external privacy SDKs suggests some privacy management, but lack of visible privacy and cookie policies reduces compliance confidence. No vulnerabilities or exposed sensitive data were detected in the analyzed content.

Recommendations

Enable DNSSEC on the domain to enhance DNS security.
Publish comprehensive privacy and cookie policies with GDPR compliance details.
Implement and publicly disclose a vulnerability disclosure program and security incident response procedures.
Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
Enhance contact information availability including security and data protection officer contacts.

Contact details published on the site

Addresses

Eteläsatama, 00170 Helsinki, Suomi (map, opens in a new tab)

Legal name

Citymapper Limited

Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company: Citymapper Limited
Description: The ultimate transport app - iPhone / Android / Web
Key services: Public transit routing, Cycle hire integration, On-demand cab booking, Real-time transport updates, Multi-modal journey planning
Content quality: good
Branding: consistent

Technology

Stack: JavaScript, Typekit fonts, Privacy Center SDK, Progressive Web App manifest
Platforms: Web, iOS, Android
Performance: moderate
Mobile: good
Accessibility: basic
SEO: good

Security

Observed score

75/100

Good practices seen

HTTPS enforced (implied by domain and app store presence)
Client transfer prohibited status on domain
Use of DNSSEC not enabled (potential improvement area)

Analytics and tracking

Tracking level: moderate
Privacy practices: basic

Advertising

Tracking pixels: privacy-center.org
Transparency: basic

Site quality

Design: good
User experience: good
Content relevance: good
Navigation: good
Professionalism: good
Trustworthiness: high

Key observations

Website is accessible with no blocking or WAF challenges.
No explicit privacy, cookie, or terms of service pages found in the provided HTML snippet.
Strong focus on transportation and urban mobility services.
Use of multiple recognized transport brands and integration with app stores.
No contact emails or phone numbers explicitly found in the provided content.
Use of external SDK for privacy management indicates some privacy awareness.
No visible security.txt or vulnerability disclosure information.
No explicit security or incident response policies found.
Good technical implementation with modern web technologies and mobile optimization.

Technical notes

Notes

The website uses a modern JavaScript-based frontend with Typekit fonts and integrates a privacy management SDK. Hosting is inferred to be on Amazon AWS based on DNS servers. The site is optimized for mobile platforms and supports progressive web app features. Performance is moderate, with potential for improvement in loading speed and accessibility features. SEO is supported by proper meta tags and Open Graph data. No CMS was detected, suggesting a custom or proprietary platform. Technical risks include lack of DNSSEC and missing security headers.

Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)

Retrieved 2026-10-25

Earlier scans of this domain

7 Jul 202548/100High45 findingsView report

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Priority findings

Network security

Critical Service Exposed: Telnet

Critical Service Exposed: SMB

Critical Service Exposed: MSSQL

Critical Service Exposed: Oracle

Critical Service Exposed: MySQL

Critical Service Exposed: RDP

Critical Service Exposed: PostgreSQL

Critical Service Exposed: Redis

Critical Service Exposed: MongoDB

High-Risk Service Exposed: FTP

High-Risk Service Exposed: RPC

High-Risk Service Exposed: NetBIOS

High-Risk Service Exposed: Elasticsearch

Security headers

Missing Strict-Transport-Security header

Missing X-Frame-Options header

Missing Content-Security-Policy header

GDPR outside view

No Cookie Consent Banner found

SSL/TLS

Weak Protocols Supported

Weak SSL Key Length

DNS health

Weak SPF Policy