Skip to main content

Security report for oauth.net

Technology · N/a

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

Security score

50/100

Risk levelMedium

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

OAuth.net is a well-established community and informational website dedicated to the OAuth open protocol, which enables secure authorization for web, mobile, and desktop applications. Founded in 2007, the site serves developers and API providers by offering specifications, code samples, articles, videos, events, and security guidance. The website positions itself as an authoritative resource in the technology sector, focusing on OAuth 2.0 and related standards. Its business model revolves around community engagement and educational content rather than direct commercial services. Technically, the site uses a straightforward stack including Bootstrap for styling, jQuery for scripting, and integrates privacy-conscious tools such as Fathom Analytics and EthicalAds for advertising. The site is mobile-optimized and provides a good user experience with clear navigation and relevant content. Hosting appears stable with NameCheap as the registrar, though no CMS or advanced hosting details are evident. From a security perspective, the site enforces HTTPS and avoids collecting sensitive user data, which reduces risk. However, it lacks important security headers and formal policies such as privacy, cookie, and incident response disclosures. No contact information or vulnerability disclosure mechanisms are provided, which could hinder trust and compliance. The domain registration is consistent and long-standing, supporting legitimacy. Overall, OAuth.net is a credible and professional resource with good content quality and technical implementation. To improve, it should implement formal privacy and cookie policies, add security headers, and provide clear contact and security incident channels to enhance compliance and trustworthiness.

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

  2. 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 oauth.net

This scan found 26 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
72
Security headers
15
Email security
70
DNS health
70
Network security
40
GDPR outside view
35
Average
50

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

OAuth.net operates as a niche community platform focused on the OAuth authorization protocol, targeting developers and API providers globally. Its competitive advantage lies in its authoritative content, community contributions, and comprehensive resource aggregation including specs, code, and educational materials. The business model is non-commercial, relying on community goodwill and ethical advertising. Growth indicators include active GitHub repository links and ongoing content updates. The partnership ecosystem includes Udemy for educational courses and EthicalAds for advertising. Strategic observations suggest the site maintains a strong position as a go-to resource for OAuth-related information but could expand by formalizing compliance and security practices to meet evolving regulatory demands.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no visible vulnerabilities or exposed sensitive data. The use of privacy-respecting analytics and ethical advertising reflects a security-conscious approach. However, the absence of security headers such as Content-Security-Policy and lack of published security policies or incident response contacts represent gaps that could be exploited or reduce user trust. There is no evidence of GDPR compliance mechanisms or vulnerability disclosure processes. The site’s security culture appears informal, typical for community-driven projects, but would benefit from formalizing security governance and transparency.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection.
  3. Publish contact information specifically for security incidents and consider adding a vulnerability disclosure or security.txt file.
  4. Enable DNSSEC on the domain to improve DNS security.
  5. Enhance accessibility features and SEO optimization to improve user experience and reach.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
An open protocol to allow secure authorization in a simple and standard method from web, mobile and desktop applications.
Key services
OAuth 2.0 specifications, Code examples, Articles and videos, Events, Books, Security guidance, Merchandise
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap CSS, jQuery 3.2.1 slim, Fathom Analytics, EthicalAds, YouTube embedded video
Frameworks
Bootstrap
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No forms collecting sensitive data
  • No exposed credentials in HTML

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Ad networks
EthicalAds
Tracking pixels
EthicalAds pixel, Fathom Analytics
Marketing tools
Fathom Analytics
Transparency
good

Site quality

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

Key observations

  1. Website is a community and informational resource for OAuth protocol
  2. No privacy, cookie, or terms of service policies found
  3. No contact emails or phone numbers explicitly provided
  4. No security or incident response policies published
  5. Uses ethical advertising and privacy-respecting analytics
  6. No forms or data collection fields present
  7. Content is technical and educational with embedded video and links
  8. No suspicious or malicious content detected
Technical notes

Notes

The website uses a simple but effective technical stack with Bootstrap and jQuery, ensuring responsive design and basic interactivity. Integration of Fathom Analytics and EthicalAds indicates a focus on privacy and ethical advertising. The site is hosted under NameCheap registrar DNS servers, with no CMS detected, suggesting a static or custom-built site. Performance is moderate with embedded YouTube content and external scripts. There is room for modernization by adopting modern JavaScript frameworks or CMS for easier content management and improved scalability. Technical risks are low but could be mitigated further by adding security headers and enabling DNSSEC.
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 oauth.net. 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 oauth.net.

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.