Skip to main content

Security report for angel.co

Technology · N/a

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

Security score

73/100

Risk levelMedium

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

The website wellfound.com is currently inaccessible due to a Cloudflare Web Application Firewall (WAF) security challenge page that blocks access to the actual site content. This challenge includes a Turnstile captcha and a message indicating a security check is in progress. As a result, no direct business descriptions, privacy policies, or terms of service are available for review. The domain is well-established, created in 1998, and uses GoDaddy as registrar with Cloudflare nameservers, indicating a mature and legitimate online presence. However, DNSSEC is not enabled, which is a minor security gap. From the technical perspective, the site leverages Cloudflare's security infrastructure, including Turnstile captcha, to protect against automated threats. The visible HTML content is minimal and focused on the security challenge, with no visible forms, social media links, or analytics scripts. Due to the blocking, no detailed assessment of the site's technical implementation, SEO, or accessibility can be made. Security posture evaluation is limited by the lack of accessible content. No security headers or policies are visible, and no vulnerability disclosures or incident response contacts are found. The domain registration data is consistent with a legitimate business, but the absence of DNSSEC and visible security policies suggests room for improvement. Overall, the site is currently not analyzable beyond the WAF challenge. The AI scoring reflects this with a low overall score due to blocked content. For a comprehensive evaluation, access to the full site content is necessary. Strategic recommendations include enabling DNSSEC, publishing clear privacy and security policies, and ensuring transparency in incident response and vulnerability disclosure.

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 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 angel.co

This scan found 16 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
57
Security headers
55
Email security
98
DNS health
90
Network security
100
GDPR outside view
35
Average
73

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

Due to the Cloudflare WAF challenge blocking access, detailed business intelligence is unavailable. The domain age and registrar data suggest a mature technology company. The contact email domain matches the website domain, indicating organizational consistency. No partner or subsidiary domains are identified. The lack of visible marketing or analytics tools limits insights into customer targeting or growth strategies.

Security posture

The security posture cannot be fully assessed due to the WAF challenge page blocking content. The use of Cloudflare's Turnstile captcha indicates a proactive approach to mitigating automated attacks. However, the absence of DNSSEC and no visible security headers or policies on the accessible page are weaknesses. No incident response or vulnerability disclosure information is available, which limits transparency and readiness assessment.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy, cookie, and terms of service policies accessible without WAF challenge.
  3. Implement and expose standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear incident response and vulnerability disclosure contacts and policies to improve trust and compliance.
  5. Review WAF challenge settings to allow legitimate users and automated scanners to access public content for transparency and SEO.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Page is a Cloudflare security challenge page with Turnstile captcha and 'Checking if the site connection is secure' message, blocking access to actual content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Technology

Stack
Cloudflare Turnstile, JavaScript, CSS animations

Analytics and tracking

Site quality

Key observations

  1. Website content is blocked by Cloudflare security challenge (WAF) preventing full content analysis.
  2. No privacy, cookie, or terms of service policies detected in the accessible content.
  3. Only contact email found is team@wellfound.com in the challenge page text.
  4. No forms or social media links detected in the provided HTML content.
  5. No security headers or meta tags visible due to blocked content.
  6. Domain is old and registered with GoDaddy, using Cloudflare nameservers without DNSSEC.
  7. Website appears to be a professional technology business but content is inaccessible for detailed analysis.
Technical notes

Notes

The website uses Cloudflare as a hosting and security provider, leveraging their Turnstile captcha for bot mitigation. The HTML content is minimal and focused on the security challenge, with CSS animations for loading indicators. No CMS or frameworks are detectable from the provided content. The absence of DNSSEC is a technical shortfall. Performance, mobile optimization, and accessibility cannot be assessed due to blocked content. The technical stack appears modern but inaccessible for deeper analysis.
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. 72/100Medium25 findingsView report
  2. 57/100Medium22 findingsView report
Reviews of this site

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

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.