Skip to main content

Security report for ogp.me

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 informational resource for the Open Graph protocol, an open standard originally created by Facebook to enable web pages to integrate rich metadata for social graph representation. The site provides detailed documentation, examples, and links to related tools and open source projects, targeting web developers and site owners interested in social media integration. The business model is centered around providing an open specification rather than commercial services, positioning itself as a foundational technology in the social web ecosystem. Technically, the site is a simple, static HTML resource with minimal JavaScript and CSS, focusing on content clarity and accessibility. It uses standard metadata tags and references HTTPS URLs but lacks advanced frameworks or CMS platforms. Performance is likely fast due to minimal resources, though mobile optimization and accessibility are basic. SEO is supported through proper meta tags and structured content. From a security perspective, the site does not present forms or user inputs, reducing attack vectors. However, no explicit security headers or privacy policies are present, and no incident response contacts are provided. The use of HTTPS is implied but not confirmed by headers data. No tracking or advertising scripts are detected, indicating a privacy-respecting approach. The domain uses privacy protection in WHOIS, which is reasonable for an open protocol site. Overall, the site is trustworthy and professional for its purpose but could improve by adding privacy and cookie policies, security headers, and contact information for security incidents. These enhancements would strengthen compliance and user trust without altering the core informational mission.

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
80
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 site operates as a niche technology resource, providing an open standard for metadata integration in social graphs. Its market position is strong within web development and social media integration communities due to its origin at Facebook and widespread adoption. The business model is non-commercial, focusing on specification dissemination and community engagement. Revenue streams are not applicable. Target customers are developers and webmasters. Growth is organic through adoption and community contributions. The ecosystem includes partnerships with major platforms like Facebook and Google, and open source tooling. Strategic observations include the importance of maintaining up-to-date documentation and expanding compliance and security transparency to support broader adoption.

Security posture

The security posture of the site is moderate. The absence of forms and user inputs reduces risk exposure. However, the lack of explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options is a gap. No privacy or cookie policies are present, which may affect GDPR compliance. Incident response readiness is not evident due to missing contact channels. No vulnerabilities or exposed sensitive data were detected in the content. The use of HTTPS URLs in metadata suggests encryption use, but SSL configuration details are unknown. Overall, the site is low risk but would benefit from enhanced security best practices and compliance documentation.

Recommendations

  1. Implement standard HTTP security headers including CSP, HSTS, and X-Frame-Options to improve security posture.
  2. Publish clear privacy and cookie policies with GDPR compliance statements to enhance legal compliance and user trust.
  3. Add explicit contact information for security incidents and data protection inquiries to improve incident response readiness.
  4. Consider adding accessibility improvements and mobile optimization enhancements to broaden usability.
  5. Maintain transparency by linking to security disclosures or vulnerability reporting mechanisms to foster community trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The Open Graph protocol enables any web page to become a rich object in a social graph. It is a specification originally created at Facebook to allow web pages to integrate with social graph functionality.
Key services
Open Graph metadata specification, Documentation and examples for implementation, Links to related tools and parsers
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS (base.css), JavaScript (basic inline script)
Performance
fast
Mobile
basic
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • Use of HTTPS URLs in metadata
  • No forms or inputs present to expose vulnerabilities

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 an informational resource about the Open Graph protocol.
  2. No forms or user input fields present, reducing attack surface.
  3. No explicit privacy, cookie, or terms of service policies found.
  4. No contact information or security incident contacts provided.
  5. Site content is static and focused on documentation and specification.
  6. No analytics or tracking scripts detected.
  7. No advertising or marketing tools detected.
  8. Site uses HTTPS URLs in metadata but actual SSL configuration unknown.
  9. No security headers detected in provided data.
  10. Open source repository link provided, indicating transparency.
Technical notes

Notes

The website is built as a static HTML page with minimal CSS and JavaScript, focusing on content delivery and documentation. The technology stack is simple and modern enough for its purpose, with no detected CMS or complex frameworks. Performance is likely fast due to low resource usage. SEO is supported by proper meta tags and structured Open Graph metadata. However, the site lacks advanced accessibility features and mobile responsiveness is basic. There is no evidence of analytics or tracking technologies, aligning with a privacy-first approach. Technical risks are minimal but could include lack of security headers and incomplete compliance documentation.
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/100Medium31 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.