Skip to main content

Security report for piey.ca

Other · N/a

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

Security score

65/100

Risk levelMedium

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

The website at https://piey.ca/lander is a minimal landing page with very limited content, primarily serving as a placeholder or initial presence for the domain. The business behind the domain is not clearly identified on the site, and no descriptive or contact information is provided. The domain was registered recently in March 2023, indicating a new or early-stage business. The site uses modern JavaScript technologies such as React and loads scripts from wsimg.com and Google Adsense for advertising purposes. However, the lack of substantive content and absence of privacy or cookie policies suggest low digital maturity. From a security perspective, the domain is registered with Go Daddy Domains Canada, Inc, with standard domain status protections but no DNSSEC enabled. The website does not present any security headers or HTTPS details in the provided data, indicating a basic security posture. No forms or user input fields are present, reducing immediate attack surface but also limiting user engagement. Advertising is handled via Google Adsense, with no additional tracking or analytics detected. Overall, the website's risk profile is moderate due to minimal content and lack of transparency rather than active vulnerabilities. The absence of privacy and cookie policies, contact information, and security best practices lowers trustworthiness and compliance standing. Strategic improvements should focus on establishing clear business identity, implementing privacy and cookie policies, enhancing security headers and HTTPS enforcement, and improving content quality to build credibility and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

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

  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

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

Keep watching piey.ca

This scan found 23 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
77
Security headers
25
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
65

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 piey.ca, from OffSeq Breach.

No leaked records found

Breach holds no records for piey.ca 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

The domain piey.ca appears to represent a new or small business entity with no publicly disclosed company name or detailed business description on the landing page. The lack of business information and contact details limits insight into market positioning or revenue streams. The use of Google Adsense suggests a potential advertising revenue model or monetization strategy. The target audience and industry sector cannot be determined from the available data. The domain registration with privacy protection is typical for early-stage businesses or those seeking anonymity. No partnerships or subsidiaries are identified. Overall, the business intelligence indicates an early-stage or placeholder web presence with limited market visibility.

Security posture

The security posture of the website is basic with no advanced protections detected. The domain status includes clientDeleteProhibited, clientTransferProhibited, and clientUpdateProhibited flags, which are positive indicators against unauthorized domain changes. However, DNSSEC is not enabled, which is a missed opportunity to secure DNS integrity. No security headers such as Content-Security-Policy or X-Frame-Options are present, increasing risk of common web attacks. The absence of HTTPS details in the data is a concern, though it may be enforced externally. No forms or user inputs reduce attack vectors but also limit functionality. No incident response or vulnerability disclosure information is available, indicating low maturity in security governance. Overall, the site requires significant improvements to meet modern security standards and compliance requirements.

Recommendations

  1. Implement and publicly display a comprehensive privacy policy and cookie policy to improve compliance and user trust.
  2. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  3. Add and configure essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Ensure HTTPS is properly configured and enforced site-wide with valid SSL/TLS certificates.
  5. Develop clear business and contact information on the website to improve credibility and user engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
JavaScript
Frameworks
React
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Google Adsense
Transparency
basic

Site quality

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

Key observations

  1. Website content is minimal and appears to be a placeholder or landing page.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or business details are provided on the page.
  4. Uses React framework and loads scripts from wsimg.com and Google Adsense.
  5. Domain is registered with Go Daddy Canada and has standard domain status flags.
  6. No DNSSEC enabled, which is a minor security concern.
  7. No security headers detected in the provided data.
  8. No HTTPS information provided; assumed basic SSL configuration due to domain registrar.
  9. No forms or user input fields detected.
  10. No social media links or emails found.
Technical notes

Notes

The website uses React as its JavaScript framework, loading scripts and styles from wsimg.com, indicating a modern front-end approach. The presence of Google Adsense scripts shows integration of advertising technology. The domain is hosted or registered via Go Daddy Domains Canada, Inc. The HTML content is minimal with no meta tags for SEO or social media (Open Graph, JSON-LD) structured data present, limiting search engine visibility and social sharing optimization. No forms or interactive elements are detected, suggesting a static landing page. Mobile optimization and accessibility are basic due to minimal content and structure. Performance is likely moderate given the small page size but cannot be fully assessed from the data. Overall, the technical implementation is minimal and could benefit from enhanced SEO, accessibility, and content development.
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 piey.ca. 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 piey.ca.

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.