Skip to main content

Security report for swymrelay.com

Other · N/a

Medium risk. 9 critical or high findings in GDPR outside view, Security headers and 2 other checks.

Security score

54/100

Risk levelMedium

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

The website swym.it is currently inaccessible due to a security verification page that blocks direct content access. This prevents a full assessment of the business, its services, and compliance posture. The domain is well-established, created in 2012, with DNSSEC enabled, indicating a legitimate registration. However, the lack of accessible content, privacy policies, contact information, and security headers limits the ability to evaluate the website's security and compliance maturity. The technical infrastructure relies heavily on JavaScript for bot detection and browser verification, which may impact user experience and accessibility. Overall, the site appears to be protected by a generic web application firewall or security mechanism, which restricts automated analysis.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

9 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. 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 swymrelay.com

This scan found 28 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
57
Security headers
20
Email security
70
DNS health
50
Network security
100
GDPR outside view
25
Average
54

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

Due to the blocked content, no direct business intelligence can be extracted from the website. The domain age suggests an established entity, but no company name, description, or services are visible. There are no visible partnerships, certifications, or trust indicators. The absence of contact details and policies reduces business credibility and transparency.

Security posture

The security posture is partially observable through the presence of DNSSEC and domain status 'ok'. However, the lack of visible HTTPS enforcement details, security headers, or incident response contacts limits the assessment. The presence of a security verification page indicates an active WAF or bot mitigation strategy, which is a positive security control but also restricts content access. No vulnerabilities or exposed sensitive data were detected due to content blocking.

Recommendations

  1. Make website content accessible to legitimate users and automated scanners to improve transparency and trust.
  2. Publish clear privacy, cookie, and terms of service policies to comply with GDPR and other regulations.
  3. Provide visible contact information including security incident response contacts.
  4. Implement and expose security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Optimize technical implementation for accessibility and SEO to improve user experience and search visibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website content is blocked by a security verification page with browser checks and JavaScript challenges indicating a WAF or security mechanism. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
JavaScript

Analytics and tracking

Site quality

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

Key observations

  1. Website content is inaccessible due to a security verification page.
  2. No visible business or contact information on the landing page.
  3. No privacy, cookie, or terms of service policies found.
  4. WHOIS data shows a long-registered domain with DNSSEC enabled.
  5. No external links or social media links detected in the HTML content.
  6. JavaScript is heavily used for browser verification and bot detection.
  7. No forms or data collection mechanisms visible.
  8. No SEO or metadata tags found due to blocked content.
  9. No security headers or SSL configuration details available from content.
  10. Analysis is incomplete due to WAF/security mechanisms.
Technical notes

Notes

The website uses JavaScript extensively for browser and network verification, indicating a sophisticated bot mitigation mechanism. No CMS or frameworks are explicitly detected. The hosting provider and SSL configuration details are not discernible from the blocked content. Performance and mobile optimization cannot be assessed. The site lacks visible metadata and SEO tags due to content blocking. Technical debt and modernization opportunities cannot be evaluated without access to the full site.
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. 66/100Medium22 findingsView report
Reviews of this site

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