Security report for pricklypearworks.com
Prickly Pear Works · Other · Malta
Medium risk. 4 critical or high findings in GDPR outside view, Email security and 2 other checks.
Prickly Pear Works is a small local business based in Malta specializing in branding, web design, and print services. The business maintains a professional presence primarily through its Facebook page, which serves as its main digital platform. The page showcases their services and recent projects, targeting local clients seeking creative and print solutions. The company appears to have a consistent brand identity and a moderate follower base, indicating a stable market position within its niche. Technically, the business leverages the Facebook platform for hosting and content delivery, utilizing modern web technologies such as React and GraphQL. The site benefits from Facebook's robust infrastructure, ensuring fast loading times and mobile optimization. However, the reliance on a third-party platform limits direct control over certain technical aspects like SEO and accessibility. From a security perspective, the page benefits from Facebook's comprehensive security measures, including HTTPS enforcement and standard security headers. No vulnerabilities or exposed sensitive data were detected. Privacy compliance is managed through Facebook's policies, with clear cookie consent mechanisms and privacy policy links. However, the business itself does not provide dedicated security or incident response information. Overall, Prickly Pear Works presents a trustworthy and professional online presence suitable for its business scale. The strategic use of Facebook as a platform offers advantages in performance and security but also imposes limitations in customization and direct control. Enhancing direct business information and security policies on a dedicated website could further improve credibility and compliance.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 63/ 100 · Medium
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (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.
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Critical
No HTTPS encryption
GDPR requires appropriate security measures for personal data
What to do: Implement SSL/TLS certificate for HTTPS
- CWE-319
- OWASP A04:2025
- ASVS V12.2.1
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- GDPR Art. 32(1)(a)
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- Critical
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
- Critical
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.
- Critical
No HTTPS Encryption
Website does not use HTTPS encryption, making all data transmission vulnerable to interception
What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS
- CWE-319
- OWASP A04:2025
- ASVS V12.2.1
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- GDPR Art. 32(1)(a)
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- Critical
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"
- CWE-1021
- OWASP A06:2025
- CAPEC-103
- ASVS V3.4.6
- OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
- RFC 7034
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching pricklypearworks.com
This scan found 16 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
- 0
- Security headers
- 70
- Email security
- 60
- DNS health
- 75
- Network security
- 100
- GDPR outside view
- 63
- Average
- 61
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
Security posture
Recommendations
- Develop and publish a dedicated security policy and incident response plan on a business-owned website or page.
- Provide clear contact channels for reporting security incidents or abuse, such as security@ or abuse@ email addresses.
- Regularly review and update third-party scripts and integrations to mitigate potential vulnerabilities.
- Enhance accessibility features to improve compliance and user experience for all visitors.
- Implement structured data and SEO best practices on a dedicated website to improve search visibility and control.
Contact details published on the site
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Prickly Pear Works
- Description
- | branding | web | print |
- Key services
- branding, web design, print
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- React, GraphQL, Relay, JavaScript, CSS
- Frameworks
- React, Relay
- Platforms
- Facebook Platform
- Performance
- fast
- Mobile
- good
- Accessibility
- basic
- SEO
- basic
Security
- Observed score
- 85/100
- Good practices seen
- HTTPS enforced
- Use of security headers
- No exposed sensitive data detected
- Secure forms with CSRF tokens
Analytics and tracking
- Services
- Facebook Analytics
- Tracking level
- moderate
- Privacy practices
- good
Advertising
- Ad networks
- Facebook Ads
- Tracking pixels
- Facebook Pixel
- Marketing tools
- Facebook Ads Manager
- Transparency
- good
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- basic
- Professionalism
- good
- Trustworthiness
- moderate
Key observations
- Website is a Facebook business page for Prickly Pear Works, a small local business in Malta specializing in branding, web, and print services.
- Content is hosted on Facebook platform with no separate website detected.
- Contact information including phone number, email, and physical address is provided on the Facebook page.
- No direct privacy or security policy pages specific to the business were found; relies on Facebook's policies.
- No signs of WAF or content blocking; full content is accessible.
- Uses Facebook's standard scripts and technologies; no vulnerable libraries detected.
- Cookie consent and privacy compliance mechanisms are present via Facebook.
- No explicit security or incident response policies found.
- No certifications or vulnerability disclosure policies found.
- Overall, the page is professionally maintained with good content quality and moderate trustworthiness.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with pricklypearworks.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review pricklypearworks.com.