Skip to main content

Security report for plainlanguage.gov

Plain Language Action and Information Network (PLAIN) · Government · United States

Low risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

76/100

Risk levelLow

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

Plainlanguage.gov is an official U.S. government website managed by the Plain Language Action and Information Network (PLAIN), a community of federal employees promoting clear and accessible government communications. The site provides comprehensive resources including guidelines, training, examples, and events to support the use of plain language across federal agencies. It is affiliated with the U.S. General Services Administration (GSA), reinforcing its authoritative position in the government sector. Technically, the website leverages modern web standards and the U.S. Web Design System (USWDS) to ensure accessibility, mobile optimization, and fast performance. It integrates Google Analytics and DigitalGov analytics for user tracking and measurement, while maintaining a clean and professional design with clear navigation and structured content. From a security perspective, the site enforces HTTPS and follows good practices by not exposing sensitive data. However, it lacks some advanced security headers and a formal security policy or incident response contact, which could be areas for improvement. Privacy compliance is moderate, with a clear privacy policy but no cookie consent mechanism detected. Overall, the website demonstrates a high level of professionalism, trustworthiness, and usability, making it a reliable resource for its target audience. The domain's WHOIS data is limited due to .gov domain policies but the affiliation with GSA and consistent branding strongly support legitimacy and trust.

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

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

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

Keep watching plainlanguage.gov

This scan found 19 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
95
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
Average
76

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

Plainlanguage.gov occupies a niche government sector focused on improving communication clarity within federal agencies. Its competitive advantage lies in official backing by the GSA and a dedicated community of federal employees. The business model is non-commercial, centered on education and resource provision. Revenue streams are not applicable as it is a government initiative. The target customers are federal employees and agencies, as well as the general public seeking clearer government communications. Growth indicators include ongoing events and community engagement. Partnerships with digital.gov and GSA enhance its ecosystem. The site’s operations reflect a stable, authoritative presence in government communications.

Security posture

The website exhibits a mature security posture with mandatory HTTPS and no visible vulnerabilities or exposed sensitive data. The absence of advanced security headers and a formal security or incident response policy indicates room for enhancement in defense-in-depth and transparency. Privacy compliance is partial, lacking cookie consent mechanisms and GDPR-specific disclosures, which may be less critical given the U.S. government context but still relevant for best practices. Incident response readiness and vulnerability disclosure mechanisms are not evident, suggesting potential gaps in security culture and communication. Overall, the site is secure but could benefit from formalizing security policies and improving privacy controls.

Recommendations

  1. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen protection against common web attacks.
  2. Add a cookie consent banner or mechanism to enhance privacy compliance and user transparency.
  3. Publish a clear security policy and incident response contact information to improve trust and preparedness.
  4. Consider creating a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Regularly review and update privacy policies to align with evolving regulations and best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Plain Language Action and Information Network (PLAIN)
Description
The Plain Language Action and Information Network (PLAIN) is a community of federal employees dedicated to the idea that citizens deserve clear communication from government. They promote plain language use in government communications to save time and money and improve public service.
Key services
Plain language guidelines, Training materials and videos, Examples of plain language usage, Resources and checklists, Community events and engagement
Content quality
excellent
Branding
consistent

Technology

Stack
Google Tag Manager, Google Analytics, US Web Design System (USWDS), JavaScript, HTML5, CSS3
Frameworks
US Web Design System
Performance
fast
Mobile
excellent
Accessibility
excellent
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure forms with proper labeling

Analytics and tracking

Services
Google Analytics, DigitalGov Universal Federated Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
DigitalGov Universal Federated Analytics
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 clear focus on plain language in government communications.
  2. Content is well-structured, comprehensive, and professionally presented.
  3. No signs of malicious or suspicious content.
  4. Good use of government branding and trust signals.
  5. No cookie consent mechanism detected, which could be improved for privacy compliance.
  6. WHOIS data is limited due to .gov domain policies.
Technical notes

Notes

The website is built using modern web technologies including HTML5, CSS3, JavaScript, and the U.S. Web Design System framework, ensuring accessibility and responsive design. It integrates Google Tag Manager and analytics tools for performance and user behavior tracking. The site loads quickly and is optimized for mobile devices. There is no detected CMS, suggesting a custom or static site architecture. Hosting details are not explicit but likely government-managed infrastructure. The technical implementation is robust with minimal technical debt, though adding advanced security headers and privacy features would further enhance the platform's resilience and 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 plainlanguage.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 plainlanguage.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.