Skip to main content

Security report for abmweb.co

Other · N/a

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

64/100

Risk levelMedium

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

The website abmweb.co is currently inaccessible due to an SSL handshake failure between Cloudflare and the origin server, resulting in a Cloudflare error 525 page. This prevents any meaningful content or business information from being accessed or analyzed. The site lacks visible privacy, cookie, or terms of service policies, and no contact information or forms are present. Technically, the site is behind Cloudflare's CDN and security services, but the origin server's SSL configuration is incompatible, causing the failure. Security posture is weak due to the inability to establish secure connections and absence of security headers or best practices. Overall, the site is effectively blocked from analysis, resulting in a low AI score and limited insights.

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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

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

Keep watching abmweb.co

This scan found 22 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
60
DNS health
75
Network security
100
GDPR outside view
35
Average
64

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention abmweb.co, from OffSeq Breach.

No leaked records found

Breach holds no records for abmweb.co right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

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 lack of accessible content and business information, no reliable business intelligence can be derived. There is no indication of company name, services, market positioning, or target audience. The site appears to be small scale or inactive given the absence of content and policies. No partnerships or subsidiaries are identifiable. The domain's WHOIS data was not provided, and thus no registration or legitimacy analysis is possible.

Security posture

The security posture is currently poor. The SSL handshake failure indicates misconfiguration or incompatibility of SSL/TLS settings on the origin server. No security headers or policies are present. There is no evidence of incident response contacts or vulnerability disclosure mechanisms. The site is protected by Cloudflare, but the protection is ineffective due to origin server issues. Compliance with GDPR or other regulations cannot be confirmed. The site is vulnerable to downtime and potential trust issues due to these failures.

Recommendations

  1. Correct the SSL configuration on the origin server to ensure compatibility with Cloudflare's SSL requirements.
  2. Implement and verify security headers such as HSTS, Content Security Policy, and X-Frame-Options.
  3. Publish clear privacy, cookie, and terms of service policies to improve compliance and trust.
  4. Add visible contact information and incident response channels to enhance business credibility and security readiness.
  5. Regularly monitor SSL certificates and server configurations to prevent future connectivity issues.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Detected Cloudflare error 525 SSL handshake failure page indicating origin server SSL misconfiguration and blocked content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Cloudflare
SEO
poor

Security

Observed score
10/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is currently inaccessible due to SSL handshake failure between Cloudflare and origin server.
  2. No meaningful content or business information is available on the landing page.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact information or forms found.
  5. No security headers or best practices observed.
  6. Website is behind Cloudflare but origin server SSL is misconfigured causing error 525.
  7. No analytics or advertising scripts detected.
  8. No social media or external business links except Cloudflare error references.
  9. Content safety is safe as only an error page is shown.
  10. Analysis incomplete due to WAF/security mechanisms. For accurate analysis, please contact guard@offseq.com
Technical notes

Notes

The website uses Cloudflare as a CDN and security provider, but the origin server's SSL configuration is incompatible, causing an SSL handshake failure (error 525). The HTML content is minimal and only displays an error page with no metadata beyond basic charset and viewport tags. No CMS, frameworks, or analytics tools are detected. The site lacks SEO optimization and accessibility features. Performance and mobile optimization cannot be assessed due to the error page. The technical debt is high due to the unresolved SSL issues and lack of content or policies.
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 abmweb.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 abmweb.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.