Skip to main content

Security report for threat.watch

Brandefense · Technology · N/a

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

Security score

75/100

Risk levelMedium

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

Threat.watch, powered by Brandefense, is a cybersecurity platform specializing in real-time monitoring of digital risks such as compromised devices, phishing domains, breached accounts, and dark web intelligence. The platform targets organizations and cybersecurity professionals seeking to assess and improve their domain security posture through free domain risk scoring and external attack surface monitoring. The website presents a professional and modern interface with clear branding and a focus on cybersecurity threat intelligence services. Technically, the website employs modern web technologies including Vue.js, Google Fonts, HubSpot analytics and marketing tools, Microsoft Clarity, and Google reCAPTCHA for form protection. The site is mobile optimized and demonstrates good SEO practices, although accessibility features are basic. Performance is moderate, with asynchronous loading of scripts and preloading of fonts to enhance user experience. From a security perspective, the site enforces HTTPS and uses reCAPTCHA to protect forms, but lacks explicit security headers and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the HTML content. Privacy compliance is limited as no privacy or cookie policies were found, and no GDPR compliance indicators are present. Business credibility is supported by professional content and branding but is weakened by the absence of contact information and transparency in WHOIS data. Overall, the website is trustworthy and functional with a moderate to good security posture. Strategic improvements include publishing comprehensive privacy and cookie policies, adding security headers, and providing clear contact information for security incidents to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

5 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Google APIs

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

  3. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching threat.watch

This scan found 19 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
77
Security headers
70
Email security
70
DNS health
80
Network security
100
GDPR outside view
50
Average
75

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

Threat.watch operates as a niche cybersecurity SaaS platform under the Brandefense brand, focusing on domain risk scoring and external attack surface monitoring. Its competitive advantage lies in providing free, real-time insights into cyber threats including phishing, compromised credentials, and dark web intelligence. The business model likely involves upselling advanced threat intelligence services or enterprise solutions. The target market includes cybersecurity teams, IT departments, and organizations concerned with digital risk exposure. The integration of marketing and analytics tools suggests active customer engagement and lead generation efforts. The absence of detailed company registration or contact data limits transparency but is typical for cybersecurity firms prioritizing privacy. The platform's partnership ecosystem is not explicitly detailed, and no related or subsidiary domains were identified.

Security posture

The security maturity of Threat.watch is moderate to good. The site uses HTTPS and reCAPTCHA to secure user input and protect against automated abuse. However, the lack of explicit security headers such as Content-Security-Policy and Strict-Transport-Security reduces defense-in-depth. No security.txt or vulnerability disclosure policies are published, which limits transparency and incident response readiness. The absence of contact channels for security incidents or abuse reports is a gap in the security culture. No exposed sensitive data or vulnerable libraries were detected, indicating good operational security practices. Compliance with GDPR or other data protection regulations is not clearly demonstrated, which may pose risks for European users. Overall, the platform shows awareness of security best practices but should enhance transparency and formalize incident response mechanisms.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve privacy compliance and user trust.
  2. Implement and advertise a vulnerability disclosure policy and security.txt file to facilitate responsible reporting.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen security posture.
  4. Provide clear contact information for security incidents, abuse reports, and general inquiries to enhance transparency.
  5. Conduct regular security audits and update compliance documentation to align with GDPR and other relevant regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Brandefense
Description
Threat.watch is a cybersecurity platform providing real-time monitoring of digital risks including compromised devices, phishing domains, email breaches, and dark web intelligence to protect data.
Key services
Domain risk scoring, Compromised device detection, Phishing domain identification, Breached account monitoring, Dark web intelligence
Content quality
good
Branding
consistent

Technology

Stack
Vue.js (implied by vue feature comments), Google Fonts, HubSpot analytics and marketing tools, Microsoft Clarity, Google reCAPTCHA, Albacross tracking
Frameworks
Vue.js
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for form protection
  • No exposed sensitive data in HTML

Analytics and tracking

Services
HubSpot Analytics, Microsoft Clarity, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
HubSpot Ads Pixel, Albacross
Tracking pixels
HubSpot Analytics, Microsoft Clarity
Marketing tools
HubSpot, Albacross, Microsoft Clarity
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. No explicit privacy, cookie, or terms of service pages found in the HTML content
  3. No direct contact emails or phone numbers visible on the homepage
  4. Site uses modern frontend technologies and integrates multiple analytics and marketing tools
  5. Focuses on cybersecurity domain risk scoring and threat intelligence
  6. No security.txt or vulnerability disclosure information found
  7. No explicit security policy or incident response contact information published
Technical notes

Notes

The website is built using modern frontend technologies, likely Vue.js, with asynchronous loading of scripts and preloading of fonts to optimize performance. It integrates multiple third-party analytics and marketing tools including HubSpot, Microsoft Clarity, Google Tag Manager, and Albacross for tracking and user engagement. The site is mobile optimized with responsive design and good SEO metadata. However, accessibility features are basic and could be improved. Hosting provider details are not disclosed. The technical implementation is solid but could benefit from enhanced security headers and formalized privacy and compliance documentation to reduce technical risks and improve user trust.
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 threat.watch. 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 threat.watch.

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.