Skip to main content

Security report for neverssl.com

Redirects to quietsublimefreshmorning.neverssl.com; the website checks ran on that page, the DNS and email checks on neverssl.com.

Technology

High risk. 4 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

49/100

Risk levelHigh

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

NeverSSL is a niche utility website designed to assist users in accessing wifi captive portals that block HTTPS redirection by providing a plain HTTP site that can be redirected to for login purposes. The site is minimalistic, with basic content and no commercial or business identity. Its market position is limited to users facing captive portal access issues, and it does not appear to operate as a commercial business. Technically, the website is simple, using only HTML and CSS without modern frameworks or CMS. It lacks HTTPS, security headers, and privacy or cookie policies, which significantly impacts its security posture. The site does not collect user data or use analytics, resulting in minimal privacy concerns but also limited compliance. Overall, the website is functional for its intended purpose but lacks professional security and compliance features.

Scanned

NIS2 and GDPR posture

NIS2 outside view
44/ 100 · High
GDPR outside view
60/ 100 · Medium
Checks completed
7of 9

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

The NIS2 figure counts only evidence anyone can see from the internet. 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. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • High

      No SPF record found

      neverssl.com publishes no SPF record, so receiving servers cannot tell which servers may send mail as this domain.

      What to do: Publish one TXT record listing your mail providers, for example "v=spf1 include:_spf.yourprovider.com -all". A domain that sends no mail should publish "v=spf1 -all".

    • High

      No DMARC record found

      There is no DMARC record at _dmarc.neverssl.com, so receivers have no instruction for mail that fails SPF and DKIM.

      What to do: Publish a TXT record at _dmarc.neverssl.com, starting with "v=DMARC1; p=none; rua=mailto:dmarc@neverssl.com" and moving to p=quarantine or p=reject once reports look clean.

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

Keep watching neverssl.com

This scan found 10 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. 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. Payments by EveryPay; 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
0
Email security
65
DNS health
95
Network security
100
Website hygiene
95
GDPR outside view
60
Average
69
After the cap
49

Not counted

  • Security headers: 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.
  • Accessibility: Accessibility is a separate readout from security, so it is reported but not scored. 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 · found on this site
  • 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

The website operates as a small-scale utility service with no evident revenue streams or business partnerships. It targets general internet users who struggle with captive portal logins on wifi networks. The business model is informational and utility-focused without commercial transactions. There are no identified partnerships, subsidiaries, or parent companies. The lack of contact information and policies suggests a low maturity level in business operations and governance.

Security posture

The security posture is weak due to the absence of HTTPS, security headers, and privacy policies. The site exposes users to risks associated with unencrypted HTTP traffic. No incident response or vulnerability disclosure mechanisms are present. While the site does not collect sensitive data, the lack of encryption and security best practices is a critical vulnerability. The use of privacy protection in WHOIS is justified given the small scale and non-commercial nature of the site.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure user connections.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish privacy and cookie policies to improve transparency and compliance.
  4. Provide clear contact information and establish an incident response contact channel.
  5. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A simple informational website designed to help users access captive portals on wifi networks by providing a non-SSL HTTP site that can be redirected to for login purposes.
Key services
Providing a non-SSL HTTP landing page to facilitate wifi login
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS3
Performance
fast
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
good
Navigation
good
Professionalism
basic
Trustworthiness
low

Key observations

  1. Website uses only HTTP, no HTTPS support.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or forms present.
  4. Minimalistic design focused on a single utility purpose.
  5. External link only to Twitter account @neverssl.
  6. No scripts or advanced technologies detected.
  7. No analytics or tracking detected.
  8. No security headers or best practices implemented.
  9. Content is safe and suitable for general audiences.
Technical notes

Notes

The website is built with basic HTML and CSS without any advanced frameworks or CMS. It is hosted on a domain that uses privacy-protected WHOIS registration. The site loads quickly due to minimal content and no external scripts. However, it lacks modern web standards such as HTTPS and security headers. There is no evidence of analytics or tracking technologies. The site is mobile accessible but with basic optimization. SEO is minimal due to lack of meta tags and structured data.
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 neverssl.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

Loading reviews…

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.