Skip to main content

Security report for manrs.org

Mutually Agreed Norms for Routing Security (MANRS) · Technology · N/a

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

Security score

74/100

Risk levelMedium

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

MANRS (Mutually Agreed Norms for Routing Security) is a globally recognized initiative focused on improving Internet routing security by establishing best practices and norms. Founded in 2014, it operates as a non-profit initiative supported by the Internet Society and partners such as the Global Cyber Alliance. The website serves as a hub for information, community engagement, training, and monitoring tools aimed at network operators, IXPs, CDN and cloud providers, and equipment vendors. The organization maintains a strong market position as a leader in routing security advocacy and community-driven governance, including a steering committee and development process.

Scanned

NIS2 and GDPR posture

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

4 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 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 Cookie Policy found

      GDPR requires clear information about cookie usage

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

    • 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

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

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

Keep watching manrs.org

This scan found 20 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
75
Security headers
50
Email security
80
DNS health
85
Network security
100
GDPR outside view
53
Average
74

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

Technical appendix

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

Business context

Business profile

MANRS operates as an important non-profit entity within the Internet security ecosystem, targeting network operators and related stakeholders globally. Its business model centers on community engagement, training, and providing tools to improve routing security. The organization benefits from partnerships with reputable entities such as the Internet Society and Global Cyber Alliance. The website content and governance structure indicate a mature and credible organization with a clear mission and active community involvement. Revenue streams are likely grant and partnership-based, typical for non-profit initiatives.

Security posture

The site demonstrates a solid security posture with HTTPS enforced and clientTransferProhibited domain status. However, DNSSEC is not enabled, and security headers like Content-Security-Policy and X-Frame-Options are not explicitly present. No vulnerability disclosure or incident response information is publicly available. The absence of a cookie consent mechanism and explicit privacy compliance features are areas for improvement. Overall, the security maturity is good but could be enhanced by adopting additional best practices and transparency measures.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and trust.
  2. Implement a cookie consent banner to comply with privacy regulations and improve user transparency.
  3. Add explicit security policy and incident response pages to enhance trust and preparedness.
  4. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Enhance HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mutually Agreed Norms for Routing Security (MANRS)
Description
MANRS is a global initiative that helps reduce the most common routing threats by setting security norms for Internet routing.
Key services
Routing security norms and best practices, Programs for network operators, IXPs, CDN/cloud providers, equipment vendors, Training and workshops, Routing security observatory and monitoring tools, Community engagement and governance
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, jQuery, Bootstrap, Slick Carousel, Google Custom Search Engine, FontAwesome
Frameworks
WordPress
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • No exposed sensitive data in HTML
  • Use of Cloudflare for DNS and security

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google Adsense
Tracking pixels
Google Analytics (via gtag)
Marketing tools
Google Custom Search Engine
Transparency
basic

Site quality

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

Key observations

  1. Website is well-structured and professionally designed.
  2. Content is comprehensive and focused on routing security.
  3. Strong community and governance presence.
  4. No direct contact emails or phone numbers publicly listed; contact via form.
  5. No explicit cookie consent mechanism found.
  6. Use of modern web technologies and security best practices.
  7. No security.txt or vulnerability disclosure page found.
  8. Social media presence on LinkedIn, Facebook, YouTube, X, and BlueSky.
  9. Use of Google Analytics and Adsense detected.
  10. No adult or questionable content detected.
Technical notes

Notes

The website is built on WordPress and leverages modern web technologies including jQuery, Bootstrap, and Slick Carousel for UI components. It uses Cloudflare for DNS and likely CDN services, ensuring fast performance and robust security. The site is mobile-optimized with good accessibility and SEO practices. Google Analytics and Google Custom Search Engine are used for analytics and search functionality. The site employs HTTPS with a strong SSL configuration but lacks DNSSEC and some recommended security headers. No cookie consent mechanism was detected, which may impact privacy compliance.
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

Earlier scans of this domain

  1. 76/100Low23 findingsView report
Reviews of this site

Share your experience with manrs.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 manrs.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.