Skip to main content

Security report for psmcode.com

Other · N/a

Partial score · DNS & email only

64/100

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

The website psmcode.com is currently inaccessible due to an SSL handshake failure between Cloudflare and the origin server, resulting in a Cloudflare error 525 page being served. This indicates a misconfiguration or incompatibility in the SSL/TLS setup on the hosting server. The domain is registered with NameCheap since 2018 and uses Cloudflare DNS servers, but DNSSEC is not enabled. No business or contact information, privacy policies, or terms of service are present on the site, and no content beyond the error page is available, limiting the ability to assess the business or technical maturity. The site appears to be a small or personal project with minimal digital footprint and no visible marketing or analytics tools.

Scanned

NIS2 and GDPR posture

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

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

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Cloudflare

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching psmcode.com

This scan found 18 issues across 5 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
Email security
40
DNS health
70
Network security
100
GDPR outside view
35
Average
64

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.

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention psmcode.com, from OffSeq Breach.

No leaked records found

Breach holds no records for psmcode.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

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 business information, it is not possible to determine the market positioning, business model, or target audience of psmcode.com. The domain age suggests some stability, but absence of contact details, social media presence, or trust indicators limits credibility. No partnerships or related domains were identified. The business intelligence is minimal and insufficient for competitive or strategic analysis.

Security posture

The security posture is weak primarily due to the SSL handshake failure preventing secure HTTPS connections. No security headers or policies are detected, and DNSSEC is not enabled, reducing DNS security. The site does not expose sensitive data but lacks visible security best practices or incident response information. The use of Cloudflare as a CDN and WAF is a positive factor, but the origin server SSL misconfiguration is a critical vulnerability impacting availability and trust.

Recommendations

  1. Correct the SSL/TLS configuration on the origin server to ensure compatibility with Cloudflare and enable full HTTPS connectivity.
  2. Enable DNSSEC to improve DNS security and trustworthiness.
  3. Publish privacy, cookie, and terms of service policies to comply with regulations and improve transparency.
  4. Add clear contact information and business details to enhance credibility and user trust.
  5. Implement standard security headers and incident response contact channels to strengthen security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Cloudflare error 525 SSL handshake failed page detected indicating origin server SSL misconfiguration and site content is blocked These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Cloudflare
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is currently inaccessible due to SSL handshake failure (Cloudflare error 525)
  2. No visible content beyond Cloudflare error page
  3. No privacy, cookie, or terms of service policies found
  4. No contact information or business details available on the page
  5. No forms or data collection mechanisms detected
  6. No social media or external business links except Cloudflare
  7. No scripts or analytics detected beyond Cloudflare styles and scripts
  8. Domain is registered with NameCheap and uses Cloudflare DNS servers
  9. DNSSEC is not enabled
  10. Website is likely small or personal project given limited data and domain age
Technical notes

Notes

The website uses Cloudflare as a CDN and DNS provider with NameCheap as the registrar. The HTML content is minimal and only serves a Cloudflare error page indicating SSL handshake failure. No CMS, analytics, or marketing technologies are detected. DNSSEC is not enabled. The site lacks SEO optimization and accessibility features due to the absence of content. Performance and mobile optimization cannot be assessed. The technical infrastructure requires remediation of SSL issues and addition of standard web technologies for improved functionality and security.
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 psmcode.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 psmcode.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.