Skip to main content

Security report for howsmyssl.com

Technology · N/a

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

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

The website 'How's My SSL?' provides an informational service focused on analyzing and reporting the SSL/TLS client security features of visitors. It targets general internet users interested in understanding their TLS version, cipher suites, and security posture. The site is technically sound, using modern web technologies such as jQuery and Bootstrap, and integrates Google Analytics for visitor tracking. The content is well-structured and informative, focusing on TLS 1.3 and related security best practices. However, the site lacks privacy, cookie, and terms of service policies, as well as any contact or business registration information, which impacts its overall trustworthiness. The WHOIS data for the domain is unavailable, indicating the domain may not be registered or WHOIS information is withheld, which raises legitimacy concerns. Security-wise, the site demonstrates excellent SSL/TLS configuration and adherence to best practices but could improve by adding security headers and incident response information.

Scanned

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

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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 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';…

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

This scan found 27 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. 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. 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
30
Email security
60
DNS health
60
Network security
100
GDPR outside view
35
Average
60

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

The website operates as a niche technical tool providing SSL/TLS client analysis and educational content. It appears to be a small-scale informational service without clear business registration or contact details. The absence of WHOIS data and business information limits the ability to assess market positioning or revenue streams. The site uses Google Analytics for user tracking and is built on common web frameworks, indicating moderate digital maturity. There is a partnership link to 'Darkish Green,' likely the developer or maintainer. The business model is informational rather than commercial, targeting users interested in internet security. Growth indicators and partnerships are minimal, and no certifications or trust badges are present.

Security posture

The website exhibits a strong security posture in terms of SSL/TLS configuration, supporting TLS 1.3, ephemeral keys for forward secrecy, session tickets, and avoiding known vulnerabilities like CRIME and BEAST. However, it lacks explicit security headers such as Content-Security-Policy and Strict-Transport-Security, which could further harden the site. No incident response or security policy information is provided, and no vulnerability disclosure or security.txt files are found. The use of Google Analytics introduces moderate user tracking, but privacy compliance is poor due to missing policies. Overall, the site is secure from a transport layer perspective but could improve in governance and transparency.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with user consent mechanisms to improve privacy compliance.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance security posture.
  3. Provide clear contact information and incident response channels to improve trust and facilitate security reporting.
  4. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Improve accessibility features and SEO metadata to enhance user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A website providing information about the SSL/TLS client used by visitors to render the page, focusing on TLS version, cipher suites, and security features.
Key services
SSL/TLS client analysis, Security feature reporting, Educational content about TLS
Content quality
good
Branding
consistent

Technology

Stack
jQuery 2.2.4, Bootstrap 3.3.7 CSS and JS, Google Analytics, Google Tag Manager
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
90/100
Good practices seen
  • Uses TLS 1.3
  • Supports ephemeral keys for forward secrecy
  • Supports session tickets
  • No TLS compression to prevent CRIME attack
  • Not vulnerable to BEAST attack
  • No insecure cipher suites used

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website provides detailed SSL/TLS client security information.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact or business registration information provided.
  4. Uses modern TLS 1.3 and secure cipher suites.
  5. Includes Google Analytics and Tag Manager for tracking.
  6. No WAF or blocking mechanisms detected.
  7. WHOIS data unavailable or domain unregistered.
Technical notes

Notes

The website uses a traditional tech stack with jQuery 2.2.4 and Bootstrap 3.3.7 for UI components, along with Google Analytics and Tag Manager for tracking. The HTML is valid and the site is mobile responsive with good navigation clarity. Performance is moderate, likely due to external dependencies on CDN-hosted libraries. No CMS or hosting provider information is detected. The site lacks modern frameworks or platforms but is stable and functional. There is room for modernization and improved accessibility compliance. No broken elements or errors were detected in the provided HTML 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

Reviews of this site

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