Skip to main content

Security report for bir.org

Other · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

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

The website bir.org currently serves a robot challenge screen implementing a client-side proof-of-work CAPTCHA mechanism to mitigate automated access. This indicates the presence of a Web Application Firewall (WAF) or similar security control actively blocking direct content access. Due to this, the actual business content is inaccessible, limiting the ability to analyze the company's services, policies, or contact information. The domain is long-established, registered since 1996 with Gandi SAS, which suggests legitimacy, but the lack of DNSSEC and visible security headers indicates room for improvement in domain and site security. Technically, the site uses advanced JavaScript cryptographic functions and Web Workers to perform the CAPTCHA challenge, demonstrating a modern approach to bot mitigation. However, the page lacks SEO optimization, accessibility features, and any visible business or compliance documentation. No privacy, cookie, or terms of service policies are present, and no contact or incident response information is available. Security posture is moderate due to the presence of the CAPTCHA challenge but is weakened by missing security headers and lack of visible SSL configuration details. The absence of privacy and cookie policies and contact information reduces compliance and trustworthiness. Overall, the site is currently inaccessible for normal users without passing the challenge, which significantly impacts user experience and trust. Strategic recommendations include enabling DNSSEC, publishing privacy and cookie policies, adding contact and incident response information, implementing security headers, and ensuring HTTPS enforcement. These steps will improve compliance, security posture, and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (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

7 findings rated critical or high. 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';…
  2. 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

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

Keep watching bir.org

This scan found 22 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. See sample alerts.

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
72
Security headers
20
Email security
85
DNS health
80
Network security
100
GDPR outside view
50
Average
68

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
  • 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 bir.org, from OffSeq Breach.

Total records
20
Employees
0
Customers
20
Third parties
0
Weak passwords
10%

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 bir.org.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

Due to the WAF challenge page, no direct business information or market positioning can be determined from the website content. The domain's long registration history suggests an established entity, but no details on business model, services, or target audience are available. The lack of contact information and policies limits insights into operational maturity or customer engagement. No partnerships or subsidiaries are identifiable from the content. The site appears to be protected by advanced security measures, possibly indicating a sensitive or high-value target, but this is speculative without further data.

Security posture

The website employs a client-side proof-of-work CAPTCHA challenge, indicating a proactive approach to mitigating automated threats and bots. However, the absence of DNSSEC, security headers, and visible SSL configuration details weakens the overall security posture. No privacy or cookie policies are published, and no incident response contacts are provided, which are gaps in compliance and transparency. The domain registration is stable and protected against unauthorized transfer. The security challenge page itself may impact legitimate user access and trust if not properly communicated or optimized.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to improve GDPR and privacy compliance.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Add clear contact information and incident response channels (e.g., security@ or abuse@ emails) to increase transparency and trust.
  5. Ensure HTTPS is properly configured and enforced site-wide with strong SSL/TLS settings.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Page is a robot challenge screen with a client-side proof-of-work CAPTCHA, indicating a WAF or security challenge blocking direct access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Description
Checking the site connection security
Content quality
poor
Branding
moderate

Technology

Stack
JavaScript, Web Crypto API, SHA1 hashing, Web Workers
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100
Good practices seen
  • Client-side proof-of-work CAPTCHA challenge

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is blocked by a security challenge page requiring client-side proof-of-work CAPTCHA.
  2. No visible business or contact information on the page.
  3. No privacy, cookie, or terms of service policies found.
  4. No forms or data collection fields present.
  5. No social media or external business-related links found except for CDN resources.
  6. Technical implementation uses advanced client-side cryptographic proof-of-work to mitigate bots.
  7. WHOIS data shows a long-registered domain with a reputable registrar but lacks DNSSEC.
  8. Page instructs users to enable cookies but does not provide a consent mechanism.
  9. No security headers or SSL configuration details available from provided data.
Technical notes

Notes

The site uses advanced JavaScript cryptographic functions and Web Workers to implement a client-side proof-of-work CAPTCHA, demonstrating a modern and resourceful approach to bot mitigation. Hosting is provided by SiteGround, as indicated by the name servers. The page loads external resources from a CloudFront CDN. The HTML is valid but minimal, with no SEO or accessibility enhancements. The site lacks meta tags for social sharing or structured data. Performance is moderate due to the computational challenge imposed by the CAPTCHA. Mobile optimization and accessibility are basic, with no ARIA roles or landmarks detected. Overall, the technical infrastructure is focused on security challenge delivery rather than content presentation.
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 bir.org. 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 bir.org.

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.