Skip to main content

Security report for statically.io

Statically · Technology · Iceland

Low risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

78/100

Risk levelLow

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

Statically is a specialized CDN service targeting developers who need fast and easy delivery of static files hosted on platforms like GitHub, GitLab, and Bitbucket. The service offers additional features such as image optimization, WordPress CDN support, screenshot generation, and avatar/OG image creation. It leverages multiple global CDN providers including Fastly, Cloudflare, and Bunny.net to ensure high performance and reliability. The business model appears to be free usage supported by sponsorships and donations, targeting a niche developer audience.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 100 · Medium
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

3 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 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching statically.io

This scan found 17 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
100
Security headers
70
Email security
60
DNS health
70
Network security
100
GDPR outside view
65
Average
78

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

Statically holds a niche position in the CDN market focused on static file delivery for developers. Its competitive advantage lies in integration with popular code hosting platforms and multi-CDN architecture. The company is relatively young, founded in 2019, and operates with a small team. Partnerships with major CDN and DNS providers enhance its service reliability. Revenue streams likely include sponsorships and donations, with no direct sales or subscription models evident. The company maintains active social media channels on Twitter and GitHub, reinforcing community engagement.

Security posture

The website enforces HTTPS and uses reputable CDN providers, which contributes to a strong security posture. Privacy and cookie policies with consent mechanisms are present, indicating GDPR awareness. However, explicit security headers like X-Frame-Options and X-Content-Type-Options are not clearly detected, and no published security policy or incident response contacts are found. The domain uses privacy protection for WHOIS, which is justified given the business type. No vulnerabilities or exposed sensitive data were detected in the HTML content. Overall, the security posture is good but could be improved with additional explicit policies and security.txt publication.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security.
  2. Add explicit security headers such as X-Frame-Options and X-Content-Type-Options.
  3. Publish a security.txt file to facilitate vulnerability disclosures.
  4. Provide clear security policy and incident response contact information on the website.
  5. Maintain and enhance privacy compliance transparency, including data retention policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Statically
Description
The CDN for developers providing fast and easy serving of static files from GitHub, GitLab, and Bitbucket with file optimization and processing.
Key services
CDN for static files, Image optimization, WordPress CDN, Screenshot generation, Avatar and OG image generation
Content quality
good
Branding
consistent

Technology

Stack
React, Tailwind CSS, Google Fonts, Google Adsense, Fastly CDN, Cloudflare CDN, Bunny.net CDN
Frameworks
React, Gatsby
Platforms
Web
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Consent mechanism for cookies and personal data

Analytics and tracking

Services
Umami (self-hosted analytics)
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Adsense
Tracking pixels
Google Funding Choices
Marketing tools
Google Adsense, Google Funding Choices
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and developer-focused services
  2. Uses multiple reputable CDN providers for performance and reliability
  3. Includes privacy and cookie policies with consent mechanisms
  4. No direct contact emails or phone numbers found on main site
  5. Social media presence on Twitter and GitHub supports legitimacy
  6. No explicit security or incident response policies published
  7. No security.txt or vulnerability disclosure found
  8. No suspicious or malicious content detected
Technical notes

Notes

Statically uses a modern technology stack including React and Gatsby for frontend, Tailwind CSS for styling, and Google Fonts for typography. The site is hosted with One.com as registrar and uses multiple CDN providers for content delivery, ensuring fast performance globally. Google Adsense is used for monetization, and Umami analytics for user tracking. The website is mobile optimized, accessible, and SEO friendly with proper meta tags and Open Graph data. No CMS is detected, indicating a custom or static site generation approach. The technical infrastructure is robust with opportunities to improve security headers and formalize vulnerability disclosure.
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. 71/100Medium25 findings · partial scanView report
Reviews of this site

Share your experience with statically.io. 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 statically.io.

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.