Skip to main content

Security report for adform.net

Technology · N/a

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

Security score

65/100

Risk levelMedium

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

The domain adform.net is registered since 2002 and appears to be associated with a technology business, likely in digital advertising or related services given the domain name. However, the website content is currently inaccessible, returning a 403 Forbidden error with minimal HTML content, indicating that access is blocked or restricted by server or security configurations. Due to this, no business descriptions, contact information, or policy documents are available for analysis. The domain uses Akamai nameservers, suggesting enterprise-level hosting infrastructure. Security posture cannot be fully assessed due to lack of accessible content and absence of security headers or SSL configuration details. Overall, the website is currently non-functional for external visitors, which severely limits trust and usability.

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

6 findings rated critical or high. Fix these first.

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

  2. 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 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';…

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

Keep watching adform.net

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
77
Security headers
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
40
Average
65

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

The domain's long registration history indicates an established presence, but the lack of accessible website content prevents detailed business intelligence analysis. No information on market positioning, services, or partnerships is available. The domain is likely important in the technology sector, possibly digital advertising, but this cannot be confirmed without content. No contact or legal information is published on the site, limiting transparency and credibility.

Security posture

The website currently returns a 403 Forbidden error, which may be due to restrictive server settings or a Web Application Firewall (WAF). No security headers or SSL details are available to evaluate. The domain registration is stable and uses Akamai for DNS, which is a positive indicator. However, the absence of accessible content and security policies on the website is a significant gap. No incident response or vulnerability disclosure information is found. Overall, the security posture is unknown but likely minimal from a visitor perspective.

Recommendations

  1. Investigate and resolve the 403 Forbidden error to restore website accessibility.
  2. Implement and publish comprehensive privacy and cookie policies to improve compliance.
  3. Add clear contact information and incident response channels to enhance trust.
  4. Enable security headers and ensure HTTPS with strong SSL/TLS configuration.
  5. Regularly audit website content and security posture to maintain transparency and protection.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error with minimal HTML content indicating access is blocked or restricted, likely by server or WAF configuration. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No metadata, scripts, forms, or external links detected in the HTML content.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact information or social media links available.
  5. Domain is well-registered and stable but website is currently blocked or restricted.
  6. No security headers or SSL configuration details available from provided data.
  7. No advertising or analytics technologies detected due to lack of content.
  8. Content safety is rated safe due to absence of content.
  9. Analysis limited by lack of accessible website content.
Technical notes

Notes

The website is hosted behind Akamai CDN as indicated by the nameservers, which suggests a robust hosting environment. However, the site currently returns a 403 Forbidden error with no additional content, metadata, or scripts detected. No CMS or frameworks are identifiable. The lack of accessible content prevents assessment of performance, SEO, mobile optimization, or accessibility. The domain registration is consistent and long-standing, but the technical implementation on the website side appears incomplete or restricted.
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. 65/100Medium31 findingsView report
  2. 65/100 −8Medium32 findingsView report
  3. 73/100Medium22 findingsView report
Reviews of this site

Share your experience with adform.net. 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 adform.net.

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.