Skip to main content

Security report for patientservicesinc.org

Other · N/a

Partial score · DNS & email only

71/100

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

The website patientservicesinc.org is currently inaccessible due to a Cloudflare error 521 indicating the origin web server is down and not responding. The domain is registered since 2009 with GoDaddy.com, LLC and uses Cloudflare as a CDN and security provider. Due to the server downtime, no business content, contact information, or policies are available for review. The website lacks privacy, cookie, and terms of service policies, and no security headers or SSL configuration details are evident from the data provided. This limits the ability to assess the company's digital maturity and security posture comprehensively. The domain registration appears consistent and legitimate, but the lack of accessible content and security best practices reduces trustworthiness and business credibility.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
6of 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

5 findings rated critical or high. Fix these first.

  1. 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

  2. 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.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching patientservicesinc.org

This scan found 15 issues across 5 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
Email security
70
DNS health
75
Network security
100
GDPR outside view
35
Average
71

Not counted

  • Security headers: did not complete in this scan.
  • 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 absence of accessible website content, no detailed business intelligence can be derived. The domain age suggests an established entity, but no information about market positioning, services, or partnerships is available. The website does not provide contact details or social media presence, limiting insights into customer engagement or growth indicators. The use of Cloudflare indicates some level of infrastructure investment, but the current downtime severely impacts operational reliability and customer trust.

Security posture

The security posture is weak due to the web server being down, which results in service unavailability. No security headers or SSL configuration details are available, and DNSSEC is not enabled, which could improve domain security. The use of Cloudflare provides some protection, but the origin server failure is a critical vulnerability affecting availability. No incident response or security policies are published, and no contact channels for security incidents are found. Overall, the security maturity appears low with significant room for improvement.

Recommendations

  1. Restore and maintain web server availability to eliminate Error 521 and ensure continuous service.
  2. Enable DNSSEC to enhance domain name system security and prevent spoofing.
  3. Publish comprehensive privacy and cookie policies to comply with GDPR and improve user trust.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Establish and publish incident response procedures and contact channels for security issues.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Page is a Cloudflare error 521 indicating the web server is down and not responding to Cloudflare requests. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
Cloudflare
SEO
poor

Security

Observed score
20/100

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 is currently inaccessible due to web server downtime (Error 521).
  2. Content is minimal and limited to Cloudflare error page with no business or contact information.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact information or forms detected.
  5. No social media or external business links except Cloudflare.
  6. Domain is registered with GoDaddy.com, LLC since 2009 with no DNSSEC enabled.
  7. Cloudflare is used as CDN and WAF but origin server is down.
  8. No security headers or SSL configuration details available from provided data.
  9. No analytics or marketing/tracking scripts detected.
  10. Content safety is rated safe due to lack of content and no adult or explicit material.
Technical notes

Notes

The website uses Cloudflare as a CDN and security provider, with domain registration through GoDaddy.com, LLC. The origin server is currently down, causing a Cloudflare 521 error. No CMS or frameworks are detected due to lack of content. The site lacks DNSSEC and security headers, and no analytics or marketing scripts are present. Performance and mobile optimization cannot be assessed due to inaccessibility. The technical infrastructure requires restoration and enhancement to improve reliability and security.
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 patientservicesinc.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 patientservicesinc.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.