Skip to main content

Security report for justthinktwice.gov

Drug Enforcement Administration · Government · United States

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

Security score

69/100

Risk levelMedium

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

The website www.justthinktwice.gov is an official U.S. government site operated by the Drug Enforcement Administration (DEA), under the U.S. Department of Justice. It serves as a comprehensive resource for drug education, prevention, and awareness targeted primarily at youth, educators, parents, and the general public. The site offers a wide range of content including drug information, news updates, true stories, consequences of drug use, and resources for living drug free. It is positioned as an authoritative source in the government sector for substance use prevention and education. Technically, the site is built on Drupal 10 CMS and leverages modern web technologies including Google Analytics, Google Tag Manager, USWDS for design consistency, and Siteimprove Analytics for quality monitoring. The site is mobile optimized, accessible, and SEO friendly, with a moderate performance profile. Security-wise, the site enforces HTTPS and anonymizes IP addresses in analytics, but lacks explicit visible security headers and a cookie consent mechanism. No vulnerabilities or exposed sensitive data were detected. Overall, the security posture is strong given the official nature and HTTPS enforcement, but could be improved by adding explicit security headers and privacy compliance features such as cookie consent. The absence of direct contact emails or phone numbers is typical for government sites that prefer contact forms. The WHOIS data is unavailable, which is common for .gov domains managed by government registries, but the domain and site branding strongly indicate legitimacy and trustworthiness. The site is safe for general audiences, contains no adult or explicit content, and provides valuable educational resources. Strategic recommendations include implementing cookie consent for GDPR compliance, publishing security and incident response policies, and enhancing security headers to further harden the site against attacks.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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 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 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 justthinktwice.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. See sample alerts.

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
80
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
Average
69

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

No leaked records found

Breach holds no records for justthinktwice.gov 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

The DEA operates this site as part of its public outreach and education mission. The site supports the DEA's broader mandate to combat drug misuse through education and prevention. The business model is government-funded public service with no commercial intent. The target audience includes youth, educators, parents, and the general public seeking reliable drug information. The site maintains a strong market position as an official government resource with high trust and authority. Content is regularly updated with news, campaigns, and educational materials. Partnerships with other government entities like the DOJ and USA.gov enhance credibility. The site does not engage in advertising or affiliate marketing, focusing solely on public health messaging.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS, anonymized analytics, and no visible sensitive data leaks. However, the lack of explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options is a minor gap. No vulnerability disclosure or incident response information is published, which is common for government sites but could be improved for transparency. The site does not implement a cookie consent mechanism, which may be a compliance gap for GDPR or other privacy regulations. Overall, the site is secure but could benefit from enhanced security header implementation and privacy compliance features.

Recommendations

  1. Implement a cookie consent banner to comply with GDPR and enhance user privacy transparency.
  2. Add and verify security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen defense against common web attacks.
  3. Publish a vulnerability disclosure policy and incident response contact information to improve transparency and security culture.
  4. Consider providing direct contact emails or phone numbers for security or general inquiries to improve user trust and communication.
  5. Regularly audit third-party scripts and analytics tools to ensure no privacy or security risks are introduced.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Drug Enforcement Administration
Description
Official U.S. government website providing drug facts, prevention information, news, and resources related to substance use and drug education.
Key services
Drug information, News and media updates, True stories, Consequences of drug use, Facts and statistics, Living drug free resources
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Analytics, Google Tag Manager, jQuery, USWDS (U.S. Web Design System), Siteimprove Analytics, AddThis social sharing
Frameworks
Drupal CMS, USWDS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Anonymize IP in Google Analytics
  • No exposed sensitive data in HTML
  • Secure forms with POST method

Analytics and tracking

Services
Google Analytics, Siteimprove Analytics, DigitalGov Web Vitals
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Siteimprove Analytics, DigitalGov Web Vitals, AddThis
Marketing tools
AddThis
Transparency
basic

Site quality

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

Key observations

  1. Official U.S. government website with .gov domain
  2. Content focused on drug education and prevention
  3. No signs of malicious or suspicious content
  4. Good use of modern web technologies and analytics
  5. No contact emails or phone numbers explicitly listed, but contact form available
  6. No cookie consent banner detected
  7. WHOIS data unavailable but expected for .gov domain
  8. No security incident or vulnerability disclosure information found
Technical notes

Notes

The site is built on Drupal 10, a modern and secure CMS platform, and uses the U.S. Web Design System (USWDS) for consistent government branding and accessibility. It integrates Google Analytics and Tag Manager for traffic analysis and Siteimprove for quality assurance. The site loads a variety of JavaScript libraries including jQuery and mmenu for navigation. Performance is moderate with responsive design and mobile optimization. No major technical debt or outdated libraries were detected. The site uses HTTPS exclusively, ensuring encrypted communications. Hosting provider details are not explicitly found but likely government infrastructure. Opportunities exist to improve security headers and implement cookie consent mechanisms.
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 justthinktwice.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 justthinktwice.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.