Is ghbtns.com Safe? Security Analysis for Mark Otto
Check if ghbtns.com is a scam or legitimate. Free security scan and reviews.
AI Summary
The website ghbtns.com is an open source project created by Mark Otto that provides unofficial GitHub buttons to display dynamic watch, fork, star, follow, and sponsor counts for GitHub repositories. It targets developers and GitHub users who want to showcase repository statistics on their sites. The project is small in scale, technology-focused, and has been active since 2012. The website is hosted on GitHub Pages with Cloudflare DNS and SSL, using Jekyll as the static site generator. It demonstrates good technical maturity with modern web standards, responsive design, and SEO optimization. Security posture is adequate with HTTPS enforced and domain status protections, but lacks DNSSEC and security headers. Privacy compliance is minimal with no privacy or cookie policies present. Overall, the site is trustworthy and professional but could improve compliance and security practices.
Detected Technologies
🧠AI Business Intelligence
Technology stack, business insights, and market analysis powered by AI.
Business Intelligence
Market & Strategic Analysis
The project occupies a niche market segment providing embeddable GitHub buttons for repository promotion. Its open source nature and Apache 2 license encourage community contributions and adoption. The business model is utility-based with no direct monetization evident. The target audience is developers and open source contributors. The website leverages partnerships with GitHub and Twitter for data and social integration. Growth indicators include longevity since 2012 and active maintenance on GitHub. The ecosystem is lightweight with minimal dependencies, focusing on simplicity and ease of use.
Security Posture Analysis
Comprehensive Security Assessment
Security maturity is moderate. The site uses HTTPS via Cloudflare Universal SSL and has domain status protections to prevent unauthorized changes. However, DNSSEC is not enabled, which could improve DNS security. No security headers such as Content-Security-Policy or Strict-Transport-Security are detected, which are recommended best practices. There is no evidence of a security policy, incident response contacts, or vulnerability disclosure mechanisms like security.txt. Privacy compliance is lacking, with no privacy or cookie policies, which may expose the project to GDPR compliance risks. No forms or sensitive data collection reduces attack surface. Overall, the security posture is adequate for a static informational site but could be enhanced.
Strategic Recommendations
Priority Actions for Security Improvement
Enable DNSSEC on the domain to improve DNS integrity and security.
✨Observations
AI-powered comprehensive website and business analysis.
AI-Enhanced Website Analysis
Business Insights
Mark Otto
A set of static buttons with dynamic watch and fork counts for any repo hosted on GitHub.
good
consistent
Technical Stack
fast
good
basic
good
Security Assessment
- HTTPS enforced via Cloudflare Universal SSL
- Domain status includes clientDeleteProhibited and other EPP protections
Analytics & Tracking
Advertising & Marketing
Website Quality Assessment
Key Observations
Website is a niche open source project for GitHub buttons.
🛡️Security Headers
HTTP security headers analysis and recommendations.
Security Headers
HTTP security headers analysis
Missing X-Frame-Options header
HIGHPrevents clickjacking attacks
Missing Content-Security-Policy header
HIGHControls resources the browser is allowed to load
Missing X-XSS-Protection header
MEDIUMLegacy XSS protection (deprecated but still recommended)
Missing Referrer-Policy header
LOWControls referrer information sent with requests
Missing Permissions-Policy header
MEDIUMControls browser features and APIs
Sensitive data may be cached
LOWCache-Control header should include "no-store" for sensitive pages
👤GDPR Compliance
Privacy and data protection assessment under GDPR regulations.
GDPR Compliance
Privacy and data protection assessment
No Privacy Policy found
HIGHGDPR requires a clear and accessible privacy policy
No Cookie Policy found
HIGHGDPR requires clear information about cookie usage
No Cookie Consent Banner found
HIGHGDPR requires explicit consent for non-essential cookies
Third-party services without privacy policy
HIGHDetected services: Twitter, Cloudflare
GDPR Compliance Analysis
🛡️NIS2 Compliance
Network & Information Security Directive compliance assessment.
NIS2 Compliance
Network & Information Security Directive
No information security framework found
HIGHNIS2 requires documented cybersecurity and information security measures
No vulnerability disclosure policy
MEDIUMNIS2 encourages coordinated vulnerability disclosure
No security policy documentation found
HIGHNIS2 requires documented cybersecurity governance and risk management
No incident response procedures found
HIGHNIS2 requires documented incident response and business continuity plans
No business continuity planning found
MEDIUMNIS2 emphasizes operational resilience and business continuity
No security contact information
HIGHNIS2 requires clear incident reporting channels
No vulnerability reporting mechanism
MEDIUMClear vulnerability reporting supports coordinated disclosure
No NIS2 reference found
LOWConsider explicitly mentioning NIS2 compliance efforts
Critical sector without clear security compliance
HIGHDetected sectors: transport, digital
📧Email Security
SPF, DKIM, and DMARC validation and email security assessment.
Email Security
SPF, DKIM, and DMARC validation
No DMARC reporting
LOWDMARC aggregate reports not configured
Strict DMARC Alignment
LOWStrict alignment may cause legitimate emails to fail
No BIMI Record
LOWBIMI displays brand logos in email clients
No MTA-STS Policy
MEDIUMMTA-STS enforces TLS for email delivery
No TLS-RPT Record
LOWTLS-RPT provides reporting for email TLS issues
SPF Details
DKIM Selectors Found
DMARC Details
🏆SSL/TLS Security
Certificate validity and encryption analysis.
SSL/TLS Security
Certificate validity and encryption analysis
SSL Certificate Expires Within 90 Days
MEDIUMSSL certificate expires in 62 days
Weak SSL Key Length
HIGHSSL certificate uses 256-bit key, which is considered weak
Partial SSL/TLS Assessment
LOWCompleted 2 of 4 security checks due to time constraints
Certificate Details
OCSP Status
📊DNS Health
DNS configuration and security assessment.
DNS Health
DNS configuration and security assessment
DNSSEC Not Enabled
MEDIUMDNSSEC is not configured for this domain
CAA Records Not Configured
LOWCertificate Authority Authorization (CAA) records not found
Domain Registration Details
DNS Records
DNSSEC Status
DNS Performance
SPF Analysis
⚡Network Security
Port scanning and network exposure analysis.
Network Security
Port scanning and network exposure analysis
Good Network Security Posture
LOWNo unnecessary services detected on common risky ports
🔧Technical Analysis
Detailed technical findings and analysis from AI assessment.
Technical Analysis
Comprehensive security assessment findings