Skip to main content

Security report for intelligence.gov

Office of the Director of National Intelligence · Government · United States

Medium risk. 6 critical or high findings in Email security, Security headers and 1 other check.

Security score

65/100

Risk levelMedium

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

The website intelligence.gov serves as the official portal for the U.S. Intelligence Community, managed by the Office of the Director of National Intelligence. It provides comprehensive information about the community's mission, organizational structure, career opportunities, and public-facing transparency initiatives including declassified documents. The site targets a broad audience including the general public, researchers, and potential intelligence community employees. The business model is informational and governmental, focusing on public education and transparency rather than commercial activities. Technically, the site is built on Joomla CMS with modern front-end technologies such as Bootstrap and jQuery. It leverages Google Tag Manager and Akamai mPulse for analytics and performance monitoring. The site is mobile optimized with good accessibility and SEO practices, though some accessibility features could be enhanced. Hosting appears to be supported by Akamai CDN, contributing to moderate performance. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. However, it lacks visible security headers and a cookie consent mechanism, which are recommended for improved security posture and privacy compliance. The absence of explicit incident response or vulnerability disclosure information is noted. WHOIS data is incomplete, which is not uncommon for government domains but reduces transparency in domain registration details. Overall, the website is professional, trustworthy, and well-maintained, with a strong focus on public trust and transparency. Strategic recommendations include enhancing privacy compliance with cookie consent, publishing security policies, and implementing additional security headers to strengthen the security posture further.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 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

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

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

Keep watching intelligence.gov

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. 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
85
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
58
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

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

Total records
2
Employees
0
Customers
2
Third parties
0
Weak passwords
0%

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 intelligence.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 site represents a key government entity responsible for coordinating the U.S. Intelligence Community. Its market position is unique as an authoritative source of intelligence community information and transparency. The business model is non-commercial, focusing on public service and information dissemination. The target audience includes citizens, academics, policy makers, and job seekers interested in intelligence careers. The site demonstrates strong branding consistency and trust signals such as official logos and .gov domain usage. Partnerships with other intelligence agencies are evident through linked domains. The site does not engage in advertising or affiliate marketing, consistent with its government status.

Security posture

The security maturity level is moderate to high, with HTTPS enforced and no visible sensitive data leaks. The site uses modern analytics tools but lacks some recommended security headers and explicit privacy mechanisms such as cookie consent banners. There is no visible vulnerability disclosure or incident response contact information, which could be improved to enhance transparency and readiness. The incomplete WHOIS data is typical for government domains but reduces external verification capability. Overall, the site demonstrates a solid security foundation but could benefit from enhanced privacy and security policy disclosures.

Recommendations

  1. Implement a visible cookie consent mechanism to comply with privacy regulations and improve user trust.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the site against common web attacks.
  3. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  4. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Enhance accessibility features to improve compliance with standards and broaden user inclusivity.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Office of the Director of National Intelligence
Description
The website represents the U.S. Intelligence Community, providing information about its mission, people, careers, and public resources. It serves as an official government portal to educate and inform the public about intelligence activities and transparency.
Key services
Public information dissemination, Career opportunities, Declassified document access, Educational resources
Content quality
excellent
Branding
consistent

Technology

Stack
Joomla CMS, jQuery, Bootstrap, Google Tag Manager, Akamai (CDN), BOOMR (performance monitoring)
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No visible sensitive data exposure
  • Use of Google Tag Manager asynchronously
  • No inline scripts with suspicious content

Analytics and tracking

Services
Akamai mPulse, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Akamai mPulse
Transparency
basic

Site quality

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

Key observations

  1. Official U.S. government intelligence community website
  2. Content is rich, well-structured, and professionally presented
  3. No signs of adult or inappropriate content
  4. No visible contact emails or phone numbers on homepage
  5. No explicit cookie consent banner detected
  6. Uses Joomla CMS with modern front-end libraries
  7. Includes Google Tag Manager and Akamai mPulse for analytics
  8. WHOIS data incomplete or restricted, typical for government domains
Technical notes

Notes

The website uses Joomla CMS with a modern front-end stack including Bootstrap and jQuery. It integrates Google Tag Manager and Akamai mPulse for analytics and performance monitoring, indicating a mature digital infrastructure. Hosting via Akamai CDN supports global content delivery and performance. The site is mobile optimized and SEO friendly, with structured navigation and rich content. Some technical debt is noted in the lack of security headers and cookie consent mechanisms. Overall, the technical implementation is solid with opportunities for modernization in security and privacy compliance.
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 intelligence.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 intelligence.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.