Skip to main content

Security report for support.xxx

Domain Protection Services, Inc. · Technology · United States

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

Security score

72/100

Risk levelMedium

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

The website support.xxx serves as a support desk platform providing user login, ticket submission, and access to a knowledge base covering billing, technical support, and user help topics. It targets users and customers requiring assistance related to support.xxx services. The business appears to be a small technology-focused support service operated under the domain protection services umbrella, with a domain registered since 2017 and hosted behind Cloudflare DNS. Technically, the site uses a modern but basic technology stack including jQuery, Bootstrap 4, Font Awesome, and Google reCAPTCHA v3 for bot protection. The site is moderately optimized for mobile and performance but lacks advanced SEO and accessibility features. No CMS or major frameworks are detected, indicating a custom or lightweight platform. From a security perspective, HTTPS is enforced and reCAPTCHA is implemented, but the absence of DNSSEC, security headers, and published privacy or cookie policies reduces the overall security posture. No contact emails or phone numbers are provided, limiting transparency and user trust. The domain registration is consistent and legitimate, with domain protection services used to safeguard ownership. Overall, the site is functional and moderately secure but lacks comprehensive privacy compliance and transparency. Strategic improvements in security headers, policy publication, and contact information would enhance trust and compliance.

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

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

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

Keep watching support.xxx

This scan found 18 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
55
Email security
85
DNS health
80
Network security
100
GDPR outside view
35
Average
72

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

support.xxx operates as a dedicated support portal for a presumably larger parent service or business. Its market positioning is as a customer service and technical support platform, focusing on user account management, ticketing, and knowledge dissemination. The business model centers on providing support services rather than direct sales. The target audience includes existing customers needing assistance with billing, technical issues, or account management. The use of domain protection services and Cloudflare indicates a focus on operational security and uptime. There is no evidence of direct revenue streams from this site, suggesting it is a service component rather than a primary business. The lack of public contact details and policies may limit customer confidence and growth potential. No partnerships or subsidiaries are evident from the data.

Security posture

The security maturity of support.xxx is moderate. HTTPS is properly implemented, and Google reCAPTCHA v3 is used to protect login forms from automated abuse. The domain status clientTransferProhibited adds a layer of domain security. However, the absence of DNSSEC and security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options is a notable gap. No privacy or cookie policies are published, which is a compliance concern under GDPR and similar regulations. The site does not expose sensitive data in the HTML, and no vulnerable libraries are detected. Incident response and security policy documentation are missing, reducing preparedness and transparency. Overall, the site would benefit from enhanced security controls and compliance documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and integrity.
  2. Publish comprehensive privacy and cookie policies to meet GDPR and other privacy regulations.
  3. Implement standard security headers (CSP, X-Frame-Options, X-Content-Type-Options) to mitigate common web attacks.
  4. Provide clear contact information including support emails and phone numbers to improve transparency and trust.
  5. Develop and publish a security policy and incident response plan to demonstrate security maturity and readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Domain Protection Services, Inc.
Description
Support desk platform for user login, ticket submission, and knowledge base access related to support.xxx services.
Key services
User login for support desk, Ticket submission, Knowledge base with billing, technical support, and user help articles
Content quality
basic
Branding
moderate

Technology

Stack
jQuery, Bootstrap 4.1.3, Font Awesome 4.7.0, Moment.js, Summernote, Bootstrap Datepicker, Bootstrap Datetimepicker, Bootstrap Colorpicker, Bootstrap Select, Multi-select jQuery plugin, Google reCAPTCHA v3
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA v3 for form protection
  • ClientTransferProhibited domain status

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Google reCAPTCHA
Transparency
poor

Site quality

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

Key observations

  1. Website is a support portal with login and ticket submission functionality.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. Use of modern JavaScript libraries and Google reCAPTCHA v3 for bot protection.
  4. No contact emails or phone numbers explicitly provided on the site.
  5. No social media or external business contact links found.
  6. Domain is registered with a domain protection service, indicating privacy focus.
  7. No DNSSEC enabled, which is a security improvement opportunity.
  8. Site uses Cloudflare DNS but no explicit Cloudflare WAF challenge detected.
  9. Site content is accessible and not blocked by WAF or security mechanisms.
Technical notes

Notes

The website uses a combination of well-known JavaScript libraries and CSS frameworks including jQuery, Bootstrap 4, Font Awesome, and various Bootstrap plugins for date picking, color picking, and multi-select functionality. Google reCAPTCHA v3 is integrated for bot mitigation on login forms. The site is hosted behind Cloudflare DNS, which provides DNS management and potential CDN services. Performance is moderate with asynchronous loading of scripts and use of CDN-hosted libraries. The site is mobile responsive with basic accessibility features but lacks advanced SEO optimizations such as meta descriptions or structured data. No CMS or major backend frameworks are detected, indicating a custom-built or lightweight platform. Technical debt appears low but modernization opportunities exist in SEO, accessibility, and security header implementation.
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 support.xxx. 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 support.xxx.

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.