Skip to main content

Security report for ogp.me

Facebook (original creator) · Technology · N/a

Medium risk. 7 critical or high findings in Security headers and GDPR outside view.

Security score

63/100

Risk levelMedium

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

The website ogp.me serves as the official specification and documentation hub for the Open Graph protocol, an open standard originally created by Facebook to enable web pages to integrate richly into social graphs. It targets web developers and digital content creators by providing detailed technical guidance and metadata standards to enhance social media sharing and interoperability. The site is positioned as a niche but critical resource within the web technology ecosystem, supported by community tools and open source resources. From a technical perspective, the site is straightforward, using standard HTML5 with RDFa-based meta tags to illustrate the protocol. It lacks modern web frameworks or CMS indications but is performant and well-structured for its purpose. Mobile optimization and accessibility are basic but sufficient given the primarily technical audience. SEO is adequately addressed through meta tags and structured data examples. Security posture is minimal; the site does not publish security headers, privacy policies, or incident response information. There is no evidence of analytics or advertising scripts, indicating a low footprint in user tracking but also a lack of transparency on data protection. The domain is legitimately registered to Facebook, consistent with the protocol's origin, and no suspicious patterns are detected. Overall, the site is a high-quality technical resource with excellent content relevance and trustworthiness but lacks formal privacy, security, and compliance disclosures. Strategic improvements in security headers, privacy policies, and contact information would enhance trust and compliance.

Scanned

This is an earlier scan of ogp.me. View the latest report

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

7 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 ogp.me

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
70
DNS health
75
Network security
100
GDPR outside view
35
Average
63

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 Open Graph protocol is a technology standard developed and maintained by Facebook (Meta Platforms, Inc.) to enable web pages to become rich objects in social graphs, primarily for social media integration. The business model is centered on open standards and community adoption rather than direct monetization. The target customers are developers and organizations seeking to optimize their web content for social sharing. The protocol enjoys widespread adoption and is a foundational technology in social media ecosystems, giving it a strong market position. The website supports the ecosystem with documentation, tools, and references to open source projects. There are no direct revenue streams or commercial services offered on the site. Partnerships are implied through references to Facebook and open source communities. The site is small in scale, focused on technical content rather than commercial operations.

Security posture

The website demonstrates a low security maturity level. It lacks published security policies, incident response contacts, and security headers that are standard best practices. There is no evidence of vulnerability disclosures or security certifications. The absence of privacy and cookie policies indicates compliance gaps with GDPR and other data protection regulations. No forms or data collection mechanisms are present, reducing attack surface but also limiting user engagement. The domain registration is legitimate and consistent, which supports trustworthiness. Overall, the security posture is minimal but without obvious vulnerabilities or exposures. Enhancements in security headers, HTTPS enforcement confirmation, and published policies would improve the security maturity and compliance stance.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve transparency and GDPR compliance.
  2. Implement and enforce security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add incident response and security contact information to support vulnerability reporting and security communications.
  4. Conduct a security audit to identify and remediate any potential vulnerabilities or outdated components.
  5. Enhance mobile optimization and accessibility features to broaden usability and compliance with web standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Facebook (original creator)
Description
The Open Graph protocol enables any web page to become a rich object in a social graph, allowing integration with social platforms such as Facebook.
Key services
Open Graph metadata specification, Technical documentation, Community tools and parsers
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, RDFa, Open Graph protocol meta tags
Performance
fast
Mobile
basic
Accessibility
basic
SEO
good

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a technical specification and documentation site for the Open Graph protocol.
  2. No privacy, cookie, or terms of service policies are present on the site.
  3. No contact information or forms are provided.
  4. No security policies or incident response information is published.
  5. No analytics or advertising scripts detected.
  6. Content is highly technical and targeted at developers.
  7. Site is accessible without WAF or blocking.
  8. No signs of suspicious or malicious content.
Technical notes

Notes

The website uses a simple, standards-compliant HTML5 structure with RDFa meta tags to illustrate the Open Graph protocol. No modern JavaScript frameworks or CMS platforms are detected. The site references external resources such as CSS and images hosted on the same domain. Performance is likely fast due to minimal scripting and content. SEO is supported by well-structured meta tags and Open Graph properties. Accessibility and mobile responsiveness are basic but adequate for the technical audience. There is no evidence of third-party analytics or advertising scripts, reducing complexity and privacy concerns. The technical stack is minimalistic, reflecting the site's role as a specification and documentation resource rather than a commercial platform.
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. 63/100 +14Medium31 findingsView report
  2. 49/100 −14High30 findingsView report
  3. 63/100Medium30 findingsView report
Reviews of this site

Share your experience with ogp.me. 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 ogp.me.

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.