Skip to main content

Security report for acl.gov

Government · N/a

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

Security score

66/100

Risk levelMedium

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

The website acl.gov is a government domain registered since 2012, hosted on Microsoft Azure with an Azure Application Gateway WAF in place. The current website content is inaccessible, returning a 403 Forbidden error page, indicating that access is blocked likely due to security configurations or firewall rules. No metadata, contact information, or business-related content is available for analysis. The domain registration is privacy protected but consistent with government domain practices. Due to the blocked content, a full assessment of the website's business model, services, and compliance posture is not possible. Security posture is weak from an external perspective due to lack of accessible content and missing security headers, but this may be due to intentional access restrictions. Overall, the site appears legitimate but inaccessible for detailed analysis.

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

7 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. 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 acl.gov

This scan found 21 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
82
Security headers
15
Email security
70
DNS health
90
Network security
100
GDPR outside view
40
Average
66

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 acl.gov, from OffSeq Breach.

Total records
7
Employees
0
Customers
7
Third parties
0
Weak passwords
57%

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for acl.gov.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

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 acl.gov is likely associated with a government agency given the .gov TLD and registrar get.gov. The domain age of over 10 years supports a mature presence. However, no public-facing content or contact details are available, limiting insights into market positioning or business operations. The lack of accessible content suggests the site may be restricted to authorized users or under maintenance. No partnerships or subsidiaries are identifiable from the data provided.

Security posture

The website is protected by Microsoft Azure Application Gateway WAF, which currently blocks access resulting in a 403 Forbidden error. No security headers or SSL configuration details are available for review. The domain lacks DNSSEC, which is recommended for enhanced DNS security. No vulnerability disclosure or incident response information is published. Privacy and cookie policies are absent, indicating potential compliance gaps. Overall, the external security posture appears minimal due to lack of accessible data, but the presence of a WAF indicates some level of security control.

Recommendations

  1. Review and adjust WAF and firewall rules to allow legitimate access while maintaining security.
  2. Publish privacy, cookie, and terms of service policies to improve transparency and compliance.
  3. Implement DNSSEC to enhance domain name system security.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Provide clear contact information and incident response channels to improve trust and security readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error with Microsoft-Azure-Application-Gateway/v2 header indicating blocking by Azure Application Gateway WAF or security configuration. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Platforms
Microsoft Azure

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 content is inaccessible due to 403 Forbidden error.
  2. No metadata, scripts, forms, or contact information available in HTML.
  3. No privacy, cookie, or terms of service policies found.
  4. No security headers or SSL configuration details available from provided data.
  5. Domain WHOIS data indicates a mature government domain with privacy protection.
  6. Hosted on Microsoft Azure platform with Azure Application Gateway WAF blocking access.
  7. No external links, social media, or business contact details found.
  8. Content safety is rated safe due to lack of content and no adult material.
  9. Analysis incomplete due to WAF/security mechanisms. For accurate analysis, please contact guard@offseq.com
Technical notes

Notes

The website is hosted on Microsoft Azure platform using Azure Application Gateway v2 as a WAF, which currently blocks access with a 403 Forbidden response. No CMS or other technologies are detectable due to lack of accessible content. The domain uses custom nameservers under acl.gov, indicating internal DNS management. DNSSEC is not enabled, which is a security improvement opportunity. Performance, SEO, and accessibility cannot be assessed due to blocked content. The technical infrastructure appears modern but access restrictions prevent 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

Reviews of this site

Share your experience with acl.gov. 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 acl.gov.

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.