Skip to main content

Security report for pagefair.com

Blockthrough · Technology · N/a

Medium risk. 5 critical or high findings in Security headers and SSL/TLS.

Security score

67/100

Risk levelMedium

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

Blockthrough is a technology company specializing in adblock revenue recovery solutions for digital publishers. Their platform enables publishers to monetize adblock users by delivering compliant, lighter ads and providing analytics and user messaging tools. The company is well-positioned in the digital advertising ecosystem, serving over 13,000 sites globally and recognized as a Google Certified Publishing Partner and IAB EU TCF v2.0 certified vendor. The website is professionally designed, content-rich, and targets publishers seeking to optimize ad revenue while maintaining user experience. Technically, the site is built on WordPress with Elementor, uses modern analytics and marketing tools, and is hosted with Cloudflare. Security posture is good with HTTPS and clientTransferProhibited domain status, though improvements in DNSSEC and security headers are recommended. Privacy compliance is supported by a detailed cookie consent mechanism, but explicit privacy policy and terms of service pages were not detected in the provided content. Overall, the site is trustworthy, well-branded, and demonstrates a mature digital presence.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 100 · Low
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 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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. 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
    • 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 pagefair.com

This scan found 23 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
37
Security headers
15
Email security
85
DNS health
70
Network security
100
GDPR outside view
95
Average
67

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

Blockthrough operates in the technology and media sectors, focusing on B2B SaaS solutions for publishers. Their business model revolves around enabling publishers to recover lost ad revenue from adblock users through compliant ad delivery and analytics. The company leverages partnerships with major ad networks and SSPs, integrating with existing ad stacks. Their market position is strong among top digital publishers, supported by multiple awards and case studies. The company shows growth indicators with extensive client base and significant revenue recovery figures. Strategic partnerships with Google, HubSpot, and others enhance their ecosystem. The absence of direct contact information on the site suggests a focus on inbound leads via demos and estimates.

Security posture

The website demonstrates a good security posture with enforced HTTPS, reputable hosting via Cloudflare, and domain status clientTransferProhibited to prevent unauthorized transfers. Cookie consent is implemented with granular control, supporting GDPR compliance. However, DNSSEC is not enabled, and common security headers like Content-Security-Policy and X-Frame-Options are not explicitly detected, representing areas for improvement. No vulnerabilities or exposed sensitive data were found in the HTML content. Incident response and security policy information are not publicly available, which could be enhanced to improve transparency and trust.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a clear privacy policy and terms of service pages accessible from the homepage.
  4. Add a security policy and incident response contact information or security.txt file to improve transparency.
  5. Consider adding explicit company contact information (email, phone, address) to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Blockthrough
Description
Blockthrough helps leading publishers generate incremental revenue by delivering lighter, nonintrusive ads to users open to seeing fewer ads. They provide adblock revenue recovery solutions, ad quality compliance, and analytics.
Key services
Adblock revenue recovery, Ad quality compliance filtering, Ad analytics and reporting, User messaging for adblock users, Integration with existing ad stacks
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Elementor, jQuery, Cloudflare, CookieYes (cookie consent), HubSpot analytics, Google Analytics, Google Tag Manager
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, HubSpot, Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google AdSense, Google AdX, Amazon, DoubleClick, LinkedIn Ads, Reddit Ads
Tracking pixels
HubSpot
Marketing tools
HubSpot, Calendly
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website uses WordPress CMS with Elementor builder.
  2. Cookie consent mechanism is implemented with detailed cookie categories.
  3. No explicit privacy policy or terms of service pages detected in the provided content.
  4. Multiple customer testimonials and case studies indicate business credibility.
  5. Security headers could be improved; DNSSEC is not enabled.
  6. No contact emails or phone numbers explicitly found in the content.
  7. Website is well-branded and professionally designed.
  8. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The website is built on a modern WordPress CMS platform using Elementor page builder, with jQuery and various third-party scripts for analytics and cookie consent. Hosting and DNS are managed by Cloudflare, providing performance and security benefits. The site loads multiple optimized images and uses responsive design techniques for mobile optimization. Analytics tools include Google Analytics, HubSpot, and Google Tag Manager, indicating a mature data collection strategy. Cookie consent is managed by CookieYes with detailed categories and user controls. Performance is moderate with room for improvement in accessibility and security headers. Overall, the technical infrastructure supports a professional and scalable digital presence.
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 pagefair.com. 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 pagefair.com.

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.