Skip to main content

Security report for pietersmit.com

Other · N/a

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

Security score

73/100

Risk levelMedium

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

The website www.pietersmit.com is a Wix-hosted site with minimal content and no visible business descriptive information. The absence of WHOIS registration data raises concerns about domain legitimacy and transparency. Technically, the site uses standard Wix technologies and polyfills, with basic mobile optimization and moderate performance. Security posture is limited, with HTTPS enabled but no security headers or privacy policies detected. The site lacks contact information and compliance indicators, reducing trustworthiness. Overall, the site appears accessible but lacks critical business and security information, suggesting a need for improved transparency and security practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
73/ 100 · Medium
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

4 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 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching pietersmit.com

This scan found 22 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
35
Email security
85
DNS health
70
Network security
100
GDPR outside view
73
Average
73

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

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 pietersmit.com, from OffSeq Breach.

No leaked records found

Breach holds no records for pietersmit.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 business descriptive content, contact details, and WHOIS data, it is difficult to ascertain the company's market position, business model, or target audience. The site appears to be a small-scale or personal portfolio site hosted on Wix. No partnerships or certifications are evident. The absence of privacy and cookie policies indicates low maturity in compliance and governance. The business intelligence is limited by the minimal publicly available information.

Security posture

The security posture of the website is basic. HTTPS is enabled, which is a positive indicator. However, no security headers such as Content-Security-Policy, X-Frame-Options, or X-Content-Type-Options were detected. There is no evidence of vulnerability disclosures, incident response contacts, or security policies. The lack of privacy and cookie policies further indicates compliance gaps. No analytics or tracking scripts were found, which reduces privacy risks but also limits user behavior insights. Overall, the site has a low security maturity level and would benefit from implementing standard security best practices and compliance documentation.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms to comply with GDPR and other regulations.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  3. Provide clear contact information including company emails and phone numbers to improve business credibility and user trust.
  4. Register the domain properly and ensure WHOIS data is available and accurate to improve legitimacy and trustworthiness.
  5. Consider adding incident response and vulnerability disclosure information to demonstrate security readiness and transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
moderate

Technology

Stack
Wix, JavaScript, Core-js, Focus-within-polyfill, Intl.Segmenter Polyfill
Platforms
Wix.com
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • HTTPS enabled

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is built on Wix platform with standard Wix scripts and assets.
  2. No WHOIS registration data found for the domain.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact emails, phone numbers, or physical addresses found on the site.
  5. No security headers detected in the provided data.
  6. No analytics or tracking services detected.
  7. Website content is minimal and lacks business descriptive information.
  8. No signs of WAF or security blocking mechanisms.
  9. Website appears accessible and functional but lacks transparency and trust signals.
Technical notes

Notes

The website is built on the Wix platform, utilizing Wix's JavaScript libraries and polyfills for browser compatibility. The site loads resources from Wix's static content delivery network. Performance is moderate with standard Wix optimizations. Mobile optimization is good due to Wix's responsive design features. Accessibility features are basic, with no advanced ARIA roles or landmarks detected. SEO optimization is minimal, with no structured data or Open Graph metadata found in the provided content. The site lacks custom frameworks or third-party integrations beyond Wix's ecosystem. Technical debt appears low but the site would benefit from enhanced SEO and accessibility improvements.
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 pietersmit.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 pietersmit.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.