Skip to main content

Security report for brobizz.com

Brobizz a/s · Transportation/trucking/railroad · Denmark

Partial score · DNS & email only

58/100

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

Scanned

5 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

3 findings rated critical or high in the checks that completed. Fix these first.

  1. 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"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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

      • 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';…

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

Keep watching brobizz.com

Only DNS and email could be checked this time. Monitoring re-checks every day and emails you when something material changes.

Daily monitoring

€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.

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

Security headers
15
Network security
100
Average
58

Not counted

  • SSL/TLS: did not complete in this scan.
  • Email security: did not complete in this scan.
  • DNS health: did not complete in this scan.
  • GDPR outside view: did not complete in this scan.
  • 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
  • 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

Technical appendix

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

Business context

Business profile

Brobizz operates in the transportation sector, providing essential payment services that facilitate toll and parking fee transactions in Scandinavia. Its long domain age and consistent branding indicate a stable market position. The business model revolves around enabling convenient payments for infrastructure usage, targeting both private and commercial users. The presence of Facebook domain verification and Google site verification suggests active digital marketing and brand protection efforts. The company leverages third-party services like Cookiebot and Matomo to manage privacy and analytics, reflecting a mature approach to digital operations. However, the absence of visible contact details and formal policies on the website may limit user trust and regulatory compliance. Strategic partnerships or subsidiary domains were not identified in the analyzed content.

Security posture

The website demonstrates a moderate security posture with mandatory HTTPS enabled and domain transfer restrictions set to clientTransferProhibited. The use of Cookiebot for consent management and Matomo for analytics indicates attention to privacy and data protection. However, the lack of DNSSEC implementation and missing security headers such as Content-Security-Policy and X-Frame-Options represent areas for improvement. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The absence of a published security policy or incident response contact channels limits transparency and readiness for security incidents. Overall, the security score is good but could be enhanced by adopting recommended best practices and publishing relevant policies.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Implement and publish a comprehensive privacy policy and terms of service on the website.
  3. Add standard security headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) to strengthen web security.
  4. Provide clear and accessible contact information including emails and phone numbers for customer support and security incidents.
  5. Develop and publish a security policy and incident response plan with dedicated contact channels to improve transparency and preparedness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Brobizz A/S
Description
Brobizz A/S – Betaling af vej- og broafgifter, parkering og færger mange steder i Skandinavien
Key services
Payment of road and bridge tolls, Parking payments, Ferry payments
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Matomo Analytics, Cookiebot, Umbraco Forms, Vimeo (embedded player)
Frameworks
Umbraco CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Client transfer prohibited domain status
  • Cookie consent management via Cookiebot

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Matomo
Marketing tools
Cookiebot
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges
  2. No explicit privacy policy or terms of service links found in the provided HTML
  3. Cookie consent is managed via Cookiebot with high confidence
  4. No contact emails or phone numbers explicitly found in the HTML content provided
  5. Use of Matomo analytics indicates privacy-conscious tracking
  6. Website uses Umbraco CMS and modern JavaScript frameworks
  7. Domain is well-established and registered with a reputable registrar
  8. No security.txt or vulnerability disclosure information found
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.

Retrieved 2026-10-25

Reviews of this site

Share your experience with brobizz.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review brobizz.com.

Feedback on this report

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

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.