Skip to main content

Security report for neverbounce.com

Other · N/a

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

Security score

66/100

Risk levelMedium

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

The website www.neverbounce.com is currently inaccessible due to a PerimeterX bot detection challenge page blocking all content access. No business information, metadata, or contact details are available for analysis. The domain WHOIS data is unavailable or the domain appears unregistered, which raises concerns about the legitimacy or current operational status of the website. The technical infrastructure includes PerimeterX for bot mitigation and Google Fonts for typography, but no further technology or CMS details can be determined. Security posture cannot be properly assessed due to lack of accessible content and headers. Overall, the site is effectively blocked from external analysis, limiting any meaningful security or compliance evaluation.

Scanned

This is an earlier scan of neverbounce.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

8 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 neverbounce.com

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
15
Email security
88
DNS health
85
Network security
100
GDPR outside view
35
Average
66

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 lack of accessible content and WHOIS data, no reliable business intelligence can be derived. The domain may be unregistered or protected, and no information about market positioning, business model, or partnerships is available. The presence of a PerimeterX challenge suggests a focus on bot mitigation, possibly indicating a high-value or sensitive service, but this cannot be confirmed. No contact or policy information is present to support credibility or compliance assessments.

Security posture

The security posture cannot be fully evaluated as the site is blocked by a bot detection mechanism. No security headers or SSL configuration details are available. The use of PerimeterX indicates an attempt to protect against automated threats, but the absence of accessible content and metadata prevents a comprehensive security analysis. No vulnerabilities or compliance gaps can be identified from the available data.

Recommendations

  1. Provide a publicly accessible landing page or information page to allow basic analysis and user access.
  2. Publish clear privacy, cookie, and terms of service policies to improve compliance and trust.
  3. Ensure WHOIS data is properly registered and publicly available to support legitimacy.
  4. Implement and expose standard security headers and HTTPS configuration for improved security posture.
  5. Offer contact information and business details to enhance credibility and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Page is a bot detection/challenge page with PerimeterX captcha blocking access to the actual website content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
PerimeterX, Roboto Google Fonts

Analytics and tracking

Advertising

Tracking pixels
PerimeterX

Site quality

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

Key observations

  1. Website content is fully blocked by a PerimeterX bot detection challenge.
  2. No actual website content, metadata, or business information is accessible.
  3. WHOIS data is unavailable or domain is unregistered.
  4. No contact, policy, or security information is present on the page.
  5. External resources are limited to PerimeterX scripts and Google Fonts.
  6. No forms, emails, phone numbers, or social media links found.
  7. Website cannot be properly analyzed due to access restrictions.
Technical notes

Notes

The website uses PerimeterX for bot detection and Google Fonts for typography. No CMS or hosting provider information is discernible. The page is a minimal challenge page with no SEO metadata or structured data. Performance and accessibility cannot be assessed due to lack of content. The technical implementation appears focused on blocking automated access rather than providing user-facing content.
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. 63/100Medium31 findingsView report
Reviews of this site

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