Skip to main content

Security report for snagged.market

Other · N/a

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

Security score

64/100

Risk levelMedium

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

The website https://www.snagged.market/loyalty currently serves a 404 error page indicating the requested content is not found. The site uses modern web technologies such as React and Next.js, and integrates third-party services like Stripe and Google Analytics. However, the lack of accessible content, absence of privacy, cookie, and terms policies, and missing contact information significantly limit the ability to assess the business or security posture. The WHOIS data is malformed and does not provide any registrar or registrant details, further reducing trust and transparency. Overall, the site appears incomplete or under development, with minimal digital maturity and poor user experience.

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

9 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 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 snagged.market

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. 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
57
Security headers
55
Email security
60
DNS health
75
Network security
100
GDPR outside view
35
Average
64

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

Due to the 404 error and lack of content, no meaningful business intelligence can be derived. There is no visible company name, description, or contact information. The domain WHOIS data is unavailable, suggesting privacy protection or data withholding. No partnerships or subsidiaries are identifiable. The site appears to be a placeholder or inactive page within the snagged.market domain.

Security posture

The security posture is weak due to the absence of visible security headers, no privacy or cookie policies, and no contact or incident response information. The site uses HTTPS (implied by URL) and includes Stripe.js for payments, but no SSL configuration details are available. The lack of security best practices and transparency poses risks if the site were to handle sensitive data. No vulnerabilities are directly visible, but the incomplete state and missing policies indicate immature security governance.

Recommendations

  1. Implement a custom 404 page with helpful navigation and branding to improve user experience.
  2. Publish comprehensive privacy, cookie, and terms of service policies to comply with legal requirements and build trust.
  3. Add clear contact information including emails and phone numbers for customer and security incident reporting.
  4. Configure and verify security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Ensure WHOIS data is complete and accurate to improve domain legitimacy and transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
React, Next.js, Stripe.js, Google Tag Manager, Google Analytics
Frameworks
Next.js
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
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 page https://www.snagged.market/loyalty returns a 404 error indicating the page is not found.
  2. WHOIS data is malformed and does not provide registrar, creation, or expiry dates.
  3. No privacy policy, cookie policy, terms of service, or contact information found on the page.
  4. No forms or user input fields detected on the page.
  5. External resources loaded include Google Fonts, Stripe.js, Google Tag Manager, and CDN assets.
  6. No social media links, emails, or phone numbers found in the HTML content.
  7. No security headers or SSL configuration details available from provided data.
  8. The site uses modern JavaScript frameworks (Next.js, React) but the content is minimal and non-functional.
  9. No evidence of adult or explicit content; content safety rating is safe.
  10. No WAF or security challenge detected; content is accessible but is an error page.
Technical notes

Notes

The site is built on Next.js and React frameworks, leveraging modern JavaScript and CSS. It loads external resources from Google Fonts, CDNJS, Stripe, and Google Tag Manager. However, the page content is minimal and returns a 404 error, indicating missing or misconfigured routing or content. No CMS or hosting provider information is discernible. Performance and accessibility cannot be fully assessed due to lack of content. SEO is poor given the missing meta descriptions and Open Graph tags with undefined values.
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 snagged.market. 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 snagged.market.

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.