Skip to main content

Security report for privacyguardian.org

PrivacyGuardian · Other · United States

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

Security score

62/100

Risk levelMedium

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

PrivacyGuardian.org operates as a domain privacy service provider that enables domain registrants to keep their personal WHOIS information private while complying with domain registration requirements. The service is offered exclusively through participating registrars at no direct cost to domain owners. The website serves as a contact and abuse reporting portal, facilitating communication between third parties and domain owners who use PrivacyGuardian's privacy service. The business targets domain registrants and registrars seeking privacy protection in domain registration data. Technically, the website is built with basic HTML, CSS, and JavaScript, incorporating Google Analytics for visitor tracking. The site includes client-side form validation and CAPTCHA mechanisms to prevent spam submissions. However, there is no evidence of modern CMS usage or advanced frameworks. Performance and mobile optimization are basic, and accessibility features are minimal. The site lacks explicit privacy and cookie policies, which impacts privacy compliance. From a security perspective, the site does not provide information about HTTPS usage or security headers, which are critical for protecting user data and preventing common web attacks. The presence of CAPTCHA and form validation are positive controls, but the absence of security headers and unclear SSL configuration reduce the overall security posture. The WHOIS data is unavailable due to privacy protection, which aligns with the business model but limits external verification of domain registration details. Overall, PrivacyGuardian.org presents a legitimate niche service with moderate business credibility but basic technical and security implementations. Strategic improvements in security headers, HTTPS enforcement, and privacy compliance documentation would enhance trust and reduce risk.

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

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

  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

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

Keep watching privacyguardian.org

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. 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
Security headers
20
Email security
70
DNS health
70
Network security
100
GDPR outside view
35
Average
62

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

PrivacyGuardian occupies a specialized niche in the domain registration ecosystem by providing WHOIS privacy services. Its business model relies on partnerships with registrars rather than direct customer engagement, which limits its public-facing contact information. The service is positioned as a free privacy layer to protect domain registrants from identity theft and spam. The company’s physical presence in Phoenix, Arizona, USA, and consistent branding support its credibility. However, the lack of detailed business data such as founding year or parent company limits deeper market analysis. The use of Google Analytics indicates some level of digital marketing awareness, but the absence of privacy policies may affect compliance with evolving data protection regulations. The company’s competitive advantage lies in its focused service offering and integration with registrars, but growth indicators and partnerships beyond registrars are not evident.

Security posture

The security maturity of PrivacyGuardian.org is basic. The site employs CAPTCHA and JavaScript validation to mitigate spam and abuse via its contact forms. However, the absence of HTTPS confirmation and missing security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options are notable gaps. No evidence of vulnerability disclosures or incident response contact emails is present beyond the abuse reporting form. The lack of privacy and cookie policies also indicates compliance gaps with GDPR and similar regulations. While the WHOIS privacy protection aligns with the business purpose, the overall security posture would benefit from enhanced transport security, explicit security policies, and documented incident response procedures. These improvements would reduce risk exposure and increase stakeholder confidence.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate and enforce secure connections site-wide.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and other data protection laws.
  3. Deploy security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the website against common attacks.
  4. Enhance mobile responsiveness and accessibility to improve user experience and compliance with accessibility standards.
  5. Establish and publish clear incident response and vulnerability disclosure procedures, including dedicated security contact channels.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PrivacyGuardian
Description
PrivacyGuardian provides domain privacy services that allow domain registrants to keep their personal information private in WHOIS records while complying with domain registration rules.
Key services
Domain WHOIS privacy protection, Contact facilitation between third parties and domain owners, Abuse reporting and handling
Content quality
basic
Branding
consistent

Technology

Stack
HTML, JavaScript, CSS, Google Analytics
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Use of CAPTCHA on forms to prevent spam
  • JavaScript validation on forms

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
good
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website provides domain privacy services and acts as a proxy contact point for domain owners.
  2. No direct contact emails or phone numbers provided; contact only via forms.
  3. WHOIS data is unavailable due to privacy protection and query failure.
  4. No privacy or cookie policy pages detected.
  5. Forms include CAPTCHA and client-side validation.
  6. Google Analytics is used for tracking.
  7. Physical address in Phoenix, Arizona, USA is provided.
  8. No social media links or security certifications found.
  9. No HTTPS or security headers information available from provided data.
Technical notes

Notes

The website is constructed using straightforward HTML, CSS, and JavaScript without reliance on modern CMS or frameworks. Google Analytics is integrated for visitor tracking, but no other third-party marketing or advertising tools are detected. The site includes client-side validation and CAPTCHA for form security. Performance is moderate, with no explicit indicators of optimization or CDN usage. Mobile optimization and accessibility are basic, suggesting potential technical debt and modernization opportunities. The absence of HTTPS information and security headers represents a technical risk that could impact user trust and data protection. Overall, the technical infrastructure supports the business function but requires upgrades to meet current web security and usability standards.
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 privacyguardian.org. 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 privacyguardian.org.

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.