Security report for bikereg.com
Other · N/a
The website www.bikereg.com appears to be an event registration platform focused on biking events. The site integrates multiple third-party analytics and tracking technologies such as Google Analytics, Facebook Pixel, Datadog RUM, and Google Tag Manager, indicating a moderate level of digital maturity. However, the absence of WHOIS registration data raises concerns about the domain's legitimacy and trustworthiness. The website lacks critical compliance documents such as privacy policies, cookie policies, and terms of service, which negatively impacts its privacy compliance score. Security posture is moderate with HTTPS enabled and use of reCAPTCHA, but no advanced security headers or incident response information is present. Overall, the site provides basic functionality but requires significant improvements in transparency, compliance, and trust indicators.
Scanned
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
1 finding rated critical or high. Fix these first.
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
- 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
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching bikereg.com
This scan found 9 issues across 4 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
- Email security
- 87
- DNS health
- 80
- Network security
- 100
- Average
- 86
- After the cap
- 75
Not counted
- Security headers: 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
Security posture
Recommendations
- Implement and publish comprehensive privacy and cookie policies to improve compliance and user trust.
- Add terms of service and incident response information to enhance transparency and preparedness.
- Improve security headers configuration to protect against common web vulnerabilities.
- Verify and update WHOIS registration information to ensure domain legitimacy and trustworthiness.
- Enhance contact information visibility with verified company emails and phone numbers.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Content quality
- poor
Technology
- Stack
- JavaScript, Google Analytics, Facebook Pixel, Datadog RUM, Google Tag Manager, reCAPTCHA, RudderLabs
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- basic
Security
- Observed score
- 60/100
- Good practices seen
- HTTPS enabled
- Use of reCAPTCHA for forms
Analytics and tracking
- Services
- Google Analytics, Datadog RUM, Facebook Pixel, Google Tag Manager, RudderLabs
- Tracking level
- extensive
- Privacy practices
- poor
Advertising
- Ad networks
- Facebook Pixel
- Tracking pixels
- Facebook Pixel, Datadog RUM, RudderLabs
- Marketing tools
- RudderLabs
- Transparency
- basic
Site quality
- Design
- basic
- User experience
- basic
- Content relevance
- poor
- Navigation
- poor
- Professionalism
- basic
- Trustworthiness
- low
Key observations
- Website is accessible and does not show WAF or security challenge.
- WHOIS data is missing, indicating possible domain registration issues.
- No privacy, cookie, or terms of service policies found on the site.
- No contact emails or phone numbers explicitly found in the content.
- Site uses multiple third-party analytics and tracking scripts.
- Site content is minimal and focused on event registration.
- No security headers detected in the provided data.
- Site uses HTTPS and reCAPTCHA for form security.
- No evidence of certifications or security frameworks.
- No incident response or vulnerability disclosure information found.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- 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
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- 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.
Reviews of this site
Share your experience with bikereg.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review bikereg.com.