Skip to main content

Security report for statically.io

Statically · Technology · Iceland

Partial score · DNS & email only

71/100

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

Statically.io is a specialized CDN service targeting developers who need fast and optimized delivery of static files hosted on popular code repositories such as GitHub, GitLab, and Bitbucket. The service integrates with these platforms to provide seamless file serving with additional features like image optimization and processing. Supported by reputable CDN partners like Fastly, Cloudflare, and Bunny.net, Statically positions itself as a reliable and developer-friendly solution in the niche CDN market. The business model is primarily free and open source, supported by sponsorships and donations, catering to a small but technically proficient audience.

Scanned

This is an earlier scan of statically.io. View the latest report

NIS2 and GDPR posture

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

4 findings rated critical or high. Fix these first.

  1. 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

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      SSL Certificate Expires Soon

      SSL certificate expires in 4 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching statically.io

This scan found 17 issues across 5 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
65
Email security
60
DNS health
65
Network security
100
GDPR outside view
65
Average
71

Not counted

  • Security headers: did not complete in this scan.
  • 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 company operates in the technology sector with a focus on developer tools and CDN services. Its competitive advantage lies in its integration with major code hosting platforms and its multi-CDN approach, leveraging top-tier CDN providers to ensure performance and reliability. The business targets developers and technical users who require efficient static file delivery and optimization. The presence of sponsorships and donation options indicates a community-supported growth strategy. Partnerships with established CDN and DNS providers enhance its infrastructure credibility. The company is relatively young, founded in 2019, and maintains a consistent brand and professional online presence.

Security posture

Statically.io demonstrates a mature security posture with HTTPS enforced, use of multiple security headers, and a comprehensive cookie consent mechanism aligned with GDPR requirements. The site does not expose sensitive data and uses privacy protection for domain registration, which is justified for its business type. However, there is no published security policy or incident response contact information, which are areas for improvement. The absence of a vulnerability disclosure or security.txt file limits transparency for security researchers. Overall, the security practices are solid but could be enhanced by formalizing policies and providing clear security contacts.

Recommendations

  1. Enable DNSSEC on the domain to strengthen DNS security and prevent spoofing.
  2. Publish a dedicated security policy and incident response page to improve transparency and trust.
  3. Provide explicit security contact channels such as security@ or abuse@ email addresses.
  4. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Regularly review and audit third-party scripts and dependencies to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Statically
Description
Statically is a CDN service for developers that serves static files from GitHub, GitLab, and Bitbucket repositories with optimization and processing capabilities.
Key services
CDN for static files, Image optimization and processing, Integration with GitHub, GitLab, Bitbucket, WordPress CDN, Screenshot and avatar generation
Content quality
good
Branding
consistent

Technology

Stack
React, Tailwind CSS, Google Fonts, FontAwesome, Google Adsense, Google Consent Mode
Frameworks
React, Gatsby
Platforms
GitHub, GitLab, Bitbucket
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • Privacy consent banner implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Reflex API
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Adsense
Tracking pixels
Google Consent Mode, Reflex API
Marketing tools
Google Adsense, Google Consent Mode
Transparency
good

Site quality

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

Key observations

  1. Website is a developer-focused CDN service with strong technical integration.
  2. Clear privacy and cookie consent mechanisms implemented.
  3. No direct company contact emails or phone numbers found on the site.
  4. Use of multiple reputable CDN partners enhances performance and reliability.
  5. Advertising is present but transparent with consent mechanisms.
  6. No explicit security or incident response policies published.
  7. WHOIS privacy protection is used but justified and not suspicious.
Technical notes

Notes

The website is built using modern web technologies including React and Gatsby, styled with Tailwind CSS, and uses Google Fonts and FontAwesome for UI elements. It integrates Google Adsense for advertising and Reflex API for analytics. The site is mobile optimized, accessible, and SEO friendly with proper meta tags and Open Graph data. Hosting and CDN services are provided by reputable partners, ensuring fast performance and global reach. The technical implementation is robust with no visible errors or broken elements. Opportunities exist to enhance DNS security and formalize security-related 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. 78/100Low25 findingsView 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.