Skip to main content

Security report for stackadapt.tech

StackAdapt · Technology · N/a

Medium risk. 5 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

StackAdapt is a recognized leader in the AdTech industry, operating a high-performance demand side platform (DSP) that handles billions of ad requests daily. Their technology blog serves as a platform to share insights and experiences from their engineering teams, focusing on scalable software development, AI integration, and user experience. The website is hosted on the Medium platform, leveraging its CMS capabilities and social features. Technically, the site employs modern technologies including Ruby on Rails and React, with a solid SSL/TLS configuration ensuring secure communications. However, performance is suboptimal with a high load time and large page size, which could impact user experience. Security posture is generally good, with proper SPF and DMARC email configurations and no critical SSL vulnerabilities, but lacks some security headers and HSTS enforcement. Privacy compliance is adequate, relying on Medium's comprehensive privacy and terms policies, though no explicit cookie consent mechanism is present. Overall, the site demonstrates a professional and trustworthy presence with room for technical and security improvements.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 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

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

      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

  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 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 stackadapt.tech

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. 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
72
Security headers
70
Email security
65
DNS health
85
Network security
100
GDPR outside view
40
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

StackAdapt positions itself strongly within the AdTech sector, targeting technology professionals and marketers interested in programmatic advertising and AI-driven solutions. Their business model revolves around providing DSP services and sharing technical knowledge to build brand credibility. The blog content reflects a medium-sized organization with a focus on software engineering excellence and innovation. The company maintains partnerships with major service providers for email and DNS management, indicating a mature operational infrastructure. Social media integration and consistent branding reinforce their market presence. The absence of explicit physical addresses or phone contacts suggests a primarily digital engagement model.

Security posture

The website benefits from HTTPS with modern TLS protocols and OCSP stapling, ensuring encrypted and validated connections. SPF and DMARC records are properly configured to protect email integrity. However, the lack of HTTP Strict Transport Security (HSTS) and other security headers like Content-Security-Policy and X-Frame-Options reduces defense-in-depth. No vulnerabilities such as Heartbleed or FREAK were detected. The site does not expose sensitive data or credentials. Incident response and security policy information are not publicly available, which may limit transparency. Overall, the security posture is solid but could be enhanced by implementing additional HTTP headers and formal security policies.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to prevent protocol downgrade attacks.
  2. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy to strengthen browser security.
  3. Introduce a cookie consent mechanism to comply with privacy regulations and improve user trust.
  4. Optimize website performance by reducing page size and resource count to improve load times and user experience.
  5. Publish explicit security policies and incident response contacts to enhance transparency and trust.
Technical notes

Notes

The website is built on the Medium CMS platform, utilizing Ruby on Rails and React technologies for content delivery and frontend interactions. Hosting is managed via Cloudflare, providing DNS and CDN services. The SSL certificate is valid with support for TLS 1.3 and 1.2, and OCSP stapling is enabled. Despite modern tech stack usage, the site suffers from slow load times (over 25 seconds) and a large number of resources (170) contributing to a page size exceeding 1MB. Accessibility and SEO optimizations are good, with proper meta tags, Open Graph, and JSON-LD structured data present. No forms are detected on the main page, indicating limited direct data collection. The site integrates Google Analytics for user tracking and social media links for engagement.
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 stackadapt.tech. 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 stackadapt.tech.

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.