Skip to main content

Security report for publicdomainregistry.com

Other · N/a

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

Security score

70/100

Risk levelMedium

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

The website publicdomainregistry.com is currently inaccessible beyond a Cloudflare Turnstile security challenge page, which blocks access to its actual content. The domain is registered with PDR Ltd. d/b/a PublicDomainRegistry.com since 2003, indicating a long-standing presence. However, due to the WAF challenge, no business content, policies, or contact information is accessible for analysis. The technical infrastructure includes Cloudflare security services, but DNSSEC is not enabled, representing a minor security gap. The website lacks visible privacy, cookie, or terms of service policies, and no forms or data collection mechanisms are present beyond the captcha challenge. Overall, the site’s security posture is moderate due to HTTPS and domain transfer protection, but content quality and privacy compliance cannot be assessed due to blocking.

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

6 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 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Cloudflare

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching publicdomainregistry.com

This scan found 21 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
75
Security headers
65
Email security
70
DNS health
75
Network security
100
GDPR outside view
35
Average
70

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

Given the domain registration and registrar information, the business behind publicdomainregistry.com appears to be a domain registration or related service provider. The lack of accessible content prevents detailed analysis of market positioning, business model, or services. The domain age suggests an established entity, but no visible partnership or subsidiary domains were found. The absence of contact details or business descriptions limits insights into customer segments or growth indicators.

Security posture

The website employs Cloudflare’s security challenge (Turnstile captcha), indicating a proactive approach to mitigating automated threats and abuse. HTTPS is enabled, and the domain status clientTransferProhibited prevents unauthorized transfers. However, DNSSEC is not enabled, and no security headers were detected in the HTML content. No incident response or security policy information is available. The blocking of content by WAF limits the ability to fully assess vulnerabilities or compliance gaps. Overall, the security posture is moderate but could be improved with DNSSEC and enhanced security headers.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies to improve GDPR and privacy compliance.
  4. Provide clear contact information including security incident response contacts.
  5. Improve website accessibility and SEO by allowing content access beyond WAF challenge and enhancing mobile optimization.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Detected Cloudflare Turnstile challenge page indicating WAF/security challenge blocking full content access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Cloudflare Turnstile, JavaScript, HTML5, CSS3
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
50/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
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 content is blocked by Cloudflare security challenge (Turnstile captcha).
  2. No visible business content, policies, or contact information available on the page.
  3. No privacy, cookie, or terms of service policies detected.
  4. No forms or data collection fields visible except hidden captcha response input.
  5. No social media links, emails, phone numbers, or addresses found.
  6. Website uses Cloudflare for security and performance.
  7. DNSSEC is not enabled which is a minor security gap.
  8. Domain is registered with a reputable registrar and has a long registration history.
  9. Website content quality and SEO are poor due to lack of accessible content.
  10. No advertising or analytics scripts detected beyond Cloudflare challenge scripts.
Technical notes

Notes

The website uses Cloudflare as a hosting and security provider, leveraging its Turnstile captcha for bot mitigation. The HTML content is minimal and primarily serves the security challenge, with no visible CMS or frameworks detected. Performance is moderate due to Cloudflare’s CDN, but content is inaccessible. The site lacks SEO meta tags and structured data. Mobile optimization and accessibility are basic due to limited content. Technical debt is low but modernization opportunities exist once content is accessible.
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

Earlier scans of this domain

  1. 70/100Medium30 findingsView report
  2. 70/100 −4Medium29 findingsView report
  3. 74/100Medium23 findingsView report
Reviews of this site

Share your experience with publicdomainregistry.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 publicdomainregistry.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.