Skip to main content

Security report for atproto.com

AT Protocol · Technology · N/a

Medium risk. 8 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

52/100

Risk levelMedium

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

AT Protocol is an open, decentralized network designed for building social applications, targeting developers and organizations interested in decentralized social networking. The website provides comprehensive technical documentation, SDKs, and guides to facilitate development on the protocol. The project is relatively new, founded in 2022, and positions itself as a technically sophisticated alternative in the social networking space. The digital infrastructure is modern, leveraging React and Next.js frameworks, with DNS managed via Cloudflare, ensuring good performance and mobile optimization. Security posture is solid with HTTPS enforced and domain protections in place, though improvements such as enabling DNSSEC and publishing security policies are recommended. Privacy compliance is currently minimal, with no visible privacy or cookie policies, which should be addressed to meet regulatory standards. Overall, the website is professional, trustworthy, and well-suited for its technical audience, but could enhance user trust and compliance by adding explicit privacy and security disclosures.

Scanned

NIS2 and GDPR posture

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

8 findings rated critical or high. Fix these first.

  1. 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.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

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

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

Keep watching atproto.com

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. 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
0
Security headers
20
Email security
70
DNS health
85
Network security
100
GDPR outside view
35
Average
52

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 AT Protocol project operates in the technology sector, focusing on decentralized social networking protocols. Its business model revolves around open protocol development and ecosystem enablement rather than direct commercial services. The target customers are developers and organizations building social applications. The project maintains a strong open-source presence on GitHub and engages with the community through technical talks and whitepapers. Market positioning is as an emerging decentralized social network protocol with a focus on technical robustness and developer empowerment. The absence of direct contact information and formal policies suggests a focus on technical users rather than general consumers. Partnerships or subsidiaries are not evident from the website content.

Security posture

The website demonstrates a good security baseline with HTTPS enforced and domain status flags preventing unauthorized domain transfers or deletions. However, DNSSEC is not enabled, which is a recommended best practice to prevent DNS spoofing. No security headers were detected in the HTML content, and there is no published security policy or incident response information, which are important for transparency and trust. No vulnerability disclosure or security.txt file is present, limiting avenues for responsible vulnerability reporting. No forms or inputs that collect sensitive data were found, reducing attack surface. Overall, the security posture is adequate but could be improved by publishing security policies, enabling DNSSEC, and adding security headers.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing attacks.
  2. Publish a comprehensive privacy policy and cookie policy to improve privacy compliance and user trust.
  3. Add a security policy and incident response information on the website to demonstrate security maturity.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
AT Protocol
Description
The AT Protocol is an open, decentralized network for building social applications.
Key services
Open protocol specifications, SDKs for development, Guides and documentation for building apps, Self-hosting personal data servers
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, JavaScript, Cloudflare DNS
Frameworks
Next.js
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by URL https://)
  • Domain status includes clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No explicit privacy, cookie, or terms of service policies found on the main site.
  3. No contact emails or phone numbers explicitly provided.
  4. Strong technical documentation and developer resources available.
  5. No advertising or tracking scripts detected.
  6. Content is highly technical and targeted at developers and technologists.
  7. Good use of Open Graph metadata for social sharing.
  8. No forms detected that collect user data on the main page.
  9. Social media presence includes Bluesky and GitHub links.
  10. No security.txt or vulnerability disclosure page found.
Technical notes

Notes

The website is built using modern web technologies including React and Next.js, providing a performant and responsive user experience. The site is well-structured with clear navigation and comprehensive technical documentation. Hosting details are not explicit, but DNS is managed via Cloudflare, indicating use of a reputable DNS provider. No CMS is detected, suggesting a custom or static site generation approach. Performance is moderate with asynchronous loading of JavaScript chunks. Accessibility and SEO optimizations are good, with proper meta tags and Open Graph data for social sharing. There is no evidence of third-party advertising or tracking scripts, indicating a privacy-conscious design. Technical risks are minimal, but the lack of DNSSEC and security headers are areas for improvement.
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

Earlier scans of this domain

  1. 61/100Medium33 findingsView report
Reviews of this site

Share your experience with atproto.com. 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 atproto.com.

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.