Skip to main content

Security report for useplaintext.email

Registrant of useplaintext.email · Technology · United Kingdom

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

Security score

53/100

Risk levelMedium

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

The website useplaintext.email serves as an educational and advocacy platform promoting the use of plain text email over HTML email. It provides detailed guidance on configuring various email clients, etiquette recommendations, and implementation advice for software developers. The site targets technical users and communities who prefer or require plain text email, positioning itself as a niche resource within the technology sector. The business model is informational, supported by the open source community and hosted on sourcehut, a known free software platform. The content quality is good, with consistent branding and trust indicators such as the 'Plain Text Certified' badge and MIT licensing. Technically, the website is built with simple HTML and CSS, hosted on sourcehut infrastructure, and exhibits good performance and mobile optimization. There are no detected CMS or complex frameworks, which aligns with the site's minimalist and security-conscious approach. Accessibility and SEO are basic to good, with clear navigation and structured content. No third-party scripts or analytics services are used, reflecting a strong privacy stance. From a security perspective, the site lacks advanced security headers and DNSSEC is not enabled, which are areas for improvement. The absence of forms or data collection reduces attack surface, and no vulnerabilities or exposed sensitive data were detected. The WHOIS data is consistent and transparent, with a domain age appropriate for the site's purpose and no privacy protection masking registrant details. However, no formal privacy, cookie, or security policies are published, which limits compliance and trust signals. Overall, the website presents a low-risk profile with a strong focus on privacy and minimalism but would benefit from enhanced security headers, formal policies, and DNSSEC implementation to improve its security posture and compliance. The business credibility is high given the clear purpose and community backing, but privacy compliance scores lower due to missing policies.

Scanned

NIS2 and GDPR posture

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

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

  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 useplaintext.email

This scan found 24 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
65
Security headers
30
Email security
60
DNS health
70
Network security
40
GDPR outside view
50
Average
53

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

The website operates as a specialized informational resource within the technology sector, focusing on email communication best practices. Its market positioning is niche, targeting technical users who value plain text email for security, privacy, and usability reasons. The business model is non-commercial and community-driven, relying on open source principles and hosted on sourcehut. Revenue streams or monetization are not evident. The target customer segment includes developers, system administrators, and privacy-conscious users. Growth indicators include active maintenance since 2019 and community contributions via public-inbox mailing lists and git repositories. The partnership ecosystem includes sourcehut and various open source email client projects referenced on the site. Strategic observations note the site's role as a trusted educational hub with potential to expand by adding more client instructions and security best practices.

Security posture

The website demonstrates a moderate security maturity level with a minimalist attack surface due to lack of forms and third-party scripts. Key strengths include the use of HTTPS (implied by domain and hosting), clientTransferProhibited domain status, and transparent WHOIS data. Vulnerabilities include absence of DNSSEC, missing security headers (CSP, HSTS, X-Frame-Options), and lack of published security or incident response policies. There are no visible compliance gaps related to GDPR or NIS2, but the absence of privacy and cookie policies limits formal compliance. Data protection practices are minimal but effective given no personal data collection. Incident response readiness is unknown due to no published contacts. The security culture is implied by the advocacy for plain text email, which reduces phishing and tracking risks. Overall, the security posture is adequate for an informational site but could be improved with standard security headers and policy disclosures.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options to harden the website against common attacks.
  3. Publish a clear privacy policy and cookie policy to improve GDPR compliance and user trust.
  4. Create and publish a security policy or security.txt file to facilitate vulnerability disclosure and incident response.
  5. Consider adding minimal analytics with privacy-respecting configurations to monitor site usage and improve user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Registrant of useplaintext.email
Description
A guide and resource site promoting the use of plain text email over HTML email, providing configuration instructions, etiquette recommendations, and implementation advice.
Key services
Guidance on configuring email clients for plain text, Recommendations for email clients, Etiquette and best practices for plain text email, Advice for software developers sending emails
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS
Platforms
sourcehut hosting
Performance
fast
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
80/100
Good practices seen
  • No forms or inputs present, reducing attack surface
  • No third-party scripts detected

Analytics and tracking

Tracking level
minimal
Privacy practices
excellent

Advertising

Transparency
excellent

Site quality

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

Key observations

  1. Website is an educational resource promoting plain text email usage.
  2. No privacy, cookie, or terms of service policies found.
  3. No forms or data collection mechanisms present.
  4. No tracking or advertising scripts detected.
  5. Content is well structured and comprehensive on the topic.
  6. No security headers detected; DNSSEC not enabled.
  7. WHOIS data is transparent and consistent with site purpose.
  8. No contact phone numbers or physical addresses found; only email contact.
  9. No social media links detected.
  10. No security or incident response policies published.
Technical notes

Notes

The website is built with clean, valid HTML5 and CSS, without reliance on JavaScript or complex frameworks, reflecting a minimalist and privacy-focused design philosophy. Hosting on sourcehut provides a stable and secure platform with good performance and mobile optimization. The absence of CMS reduces attack surface and technical debt. SEO is basic but sufficient for the niche audience. The site lacks advanced technical features such as structured data (JSON-LD) or Open Graph metadata, which could improve search visibility and social sharing. No external scripts or analytics are used, enhancing privacy but limiting usage insights. Overall, the technical implementation is solid for the site's purpose but could be modernized with enhanced metadata and security features.
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 useplaintext.email. 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 useplaintext.email.

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.