Security report for go-aheadnordic.no

Name: Dark-web exposure summary for go-aheadnordic.no
Creator: OffSeq Breach

Go-Ahead Nordic · Transportation · Norway

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

Security score

49/100

Risk levelHigh

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

Go-Ahead Nordic operates as a regional train service provider in Norway, connecting major cities such as Oslo, Stavanger, and Kristiansand. The company is part of the larger Go-Ahead Group and focuses on delivering passenger rail services with an emphasis on travel information and customer support. The website serves as a portal for travelers to plan journeys, check train status, and access company news. Technically, the site is built on a modern React single-page application hosted on Microsoft Azure, integrating analytics and marketing tools such as Google Analytics, Bing Ads, and Telia ACE Web SDK. The site demonstrates good mobile optimization, accessibility, and basic SEO practices. Security posture is solid with HTTPS enforced and cookie consent mechanisms in place, though additional security headers and published security policies would enhance trust. Overall, the domain registration aligns well with the business profile, indicating legitimacy and consistency. The site is safe for general audiences and does not contain any adult or questionable content.

Scanned

NIS2 and GDPR posture

GDPR outside view: 50/ 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

18 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 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 Privacy Policy found
  GDPR requires a clear and accessible privacy policy
  What to do: Add a comprehensive privacy policy page and link to it prominently
  References
  - GDPR Art. 12
  - GDPR Art. 13
  - NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- 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
- High
  Third-party services without privacy policy
  Detected services: Google Analytics, Facebook, YouTube
  What to do: Document all third-party data sharing in your privacy policy
  References
  - GDPR Art. 13(1)(e)
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 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

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

Keep watching go-aheadnordic.no

This scan found 31 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: 75
Security headers: 65
Email security: 70
DNS health: 75
Network security: 0
GDPR outside view: 50
Average: 56
After the cap: 49

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 go-aheadnordic.no, from OffSeq Breach.

Total records: 38
Employees: 0
Customers: 38
Third parties: 0
Weak passwords: 0%

3 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 go-aheadnordic.no.

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

Go-Ahead Nordic holds a strategic position as a regional rail operator in Norway, leveraging the Go-Ahead Group's expertise. Their business model centers on public transportation services, targeting Norwegian train travelers. The company benefits from a clear brand presence and active social media engagement, which supports customer outreach and brand trust. Revenue streams likely derive from government contracts and ticket sales. The website content and structure reflect a customer-centric approach with travel updates and service information. Partnerships with platforms like Entur and use of Telia's ACE Web SDK indicate integration with national transport ecosystems. Growth indicators include recent service updates and seasonal promotions. The company maintains a medium-sized operational scale with a focus on regional connectivity.

Security posture

The website exhibits a mature security posture with mandatory HTTPS and cookie consent management aligned with GDPR. Security headers such as cache-control are present, but critical headers like Content-Security-Policy and Strict-Transport-Security are missing, representing an area for improvement. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the absence of a published security policy, incident response contacts, or vulnerability disclosure program limits transparency and readiness perception. The use of third-party analytics and advertising scripts introduces moderate tracking but is managed with user consent. Overall, the security maturity is good but could be enhanced by formalizing security governance and improving header configurations.

Recommendations

Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the site against common web attacks.
Publish a dedicated security policy page and provide clear incident response contact channels such as security@ or abuse@ email addresses.
Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
Enhance privacy transparency by detailing data retention policies and cookie usage in the cookie policy.
Regularly audit third-party scripts and tracking tools to minimize privacy risks and improve user trust.

Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company: Go-Ahead Nordic
Description: Go-Ahead Nordic operates train services in Norway, connecting cities such as Oslo, Stavanger, Kristiansand, and others. They provide travel information, ticketing, and customer service for rail passengers.
Key services: Passenger train services, Travel information, Customer support
Content quality: good
Branding: consistent

Technology

Stack: React, Google Tag Manager, Google Analytics, Bing Ads, Telia ACE Web SDK
Frameworks: React
Platforms: Azure Web Apps
Performance: moderate
Mobile: good
Accessibility: good
SEO: basic

Security

Observed score

85/100

Good practices seen

HTTPS enforced
No exposed sensitive data in HTML
Consent management for cookies

Analytics and tracking

Services: Google Analytics, Bing Ads
Tracking level: moderate
Privacy practices: good

Advertising

Ad networks: Bing Ads
Tracking pixels: Bing Ads pixel
Marketing tools: Bing Ads, Telia ACE Web SDK
Transparency: basic

Site quality

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

Key observations

Website is a professional public transportation service site for Go-Ahead Nordic in Norway.
Uses modern web technologies and analytics tools.
Includes cookie consent and privacy policy in Norwegian language.
No direct contact emails or phone numbers found on the homepage HTML.
Social media presence on Facebook, YouTube, and Instagram is clearly linked.
No visible security policy or incident response contacts published.
No vulnerability disclosure or security.txt found.
Good SSL and basic security headers present but could be improved.

Technical notes

Notes

The website is a React-based single-page application hosted on Microsoft Azure, leveraging modern JavaScript frameworks and asynchronous script loading for performance. Integration with Google Tag Manager, Google Analytics, and Bing Ads supports marketing and analytics needs. The use of Telia ACE Web SDK indicates advanced visitor management capabilities. The site demonstrates good mobile responsiveness and accessibility features such as ARIA labels and keyboard navigation aids. SEO is basic with meta tags present but could be improved with richer structured data. Performance is moderate, with deferred script loading helping page speed. Technical risks include reliance on multiple third-party scripts which may impact privacy and security if not regularly reviewed. Overall, the technical infrastructure is modern and well-implemented with opportunities for optimization and security enhancements.

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

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 Content-Security-Policy header

GDPR outside view

No Privacy Policy found

No Cookie Consent Banner found

Third-party services without privacy policy

SSL/TLS

Weak SSL Key Length

Keep watching go-aheadnordic.no

Daily monitoring

Full report

Results by check

Security headers, 4 findings, score 65/100

SSL/TLS, 3 findings, score 75/100

Email security, 4 findings, score 70/100

DNS health, 3 findings, score 75/100

Network security, 14 findings, score 0/100

GDPR outside view, 3 findings, score 50/100

NIS2 outside view, Earlier method, rescan for details · not counted in the security score–