Skip to main content

Security report for hiram.io

Swyftlight · Technology · United States

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

72/100

Risk levelMedium

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

The website hiram.io represents a solopreneur and indie hacker named Hiram Núñez, operating under the organization Swyftlight. The business focuses on building and launching multiple digital projects aimed at improving the web, with an emphasis on privacy, no-code/low-code development, and emerging technologies. The site showcases a portfolio of ventures including privacy-respecting analytics, digital product sales, and consulting services. The market position is niche but credible, targeting tech enthusiasts, startups, and business strategists. Technically, the site is built on the Dorik platform, uses modern JavaScript libraries like jQuery and Typed.js, and is hosted and registered via Cloudflare, ensuring reliable infrastructure. The site is mobile optimized and has good SEO practices, though accessibility is basic. Security posture is moderate with HTTPS enforced and clientTransferProhibited domain status, but lacks DNSSEC and security headers. Privacy compliance is limited due to absence of privacy and cookie policies. Overall, the site is professional and trustworthy but would benefit from enhanced compliance and security disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
73/ 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

4 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 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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

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

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

      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 hiram.io

This scan found 20 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
75
Security headers
50
Email security
60
DNS health
75
Network security
100
GDPR outside view
73
Average
72

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

Hiram operates as a small-sized solopreneur business with multiple side projects and ventures under the Swyftlight umbrella. The business model is based on product development, consulting, and digital sales, leveraging no-code tools and open source. The target audience includes solopreneurs, startups, and tech-savvy users interested in privacy and emerging tech. The portfolio approach diversifies revenue streams and market reach. The presence of privacy-respecting analytics and multiple project sites indicates a focus on ethical technology and community engagement. The LinkedIn and Mastodon profiles enhance professional networking and outreach. The business shows growth potential through continuous project launches and public building approach.

Security posture

The website demonstrates a moderate security maturity level. HTTPS is enforced, and the domain has clientTransferProhibited status, reducing transfer risks. However, DNSSEC is not enabled, which is a recommended best practice to prevent DNS spoofing. No explicit security headers were detected, which could expose the site to certain web-based attacks. The contact form includes a honeypot field to mitigate spam, indicating some security awareness. There is no published security policy or incident response contact, which limits transparency and readiness for security incidents. Privacy compliance is partial, lacking privacy and cookie policies, which is a compliance gap especially under GDPR. Overall, the security posture is adequate for a small solopreneur site but could be improved with standard security headers, DNSSEC, and published policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a comprehensive privacy policy and cookie policy to improve GDPR and privacy compliance.
  4. Add a security policy and incident response contact information to increase transparency and preparedness.
  5. Consider adding direct contact emails or phone numbers for business and security inquiries to improve trust and communication.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Swyftlight
Description
I build projects to improve our world—in public, and share lessons along the way. At the intersection of tech, business, open source, startups, and no-code.
Key services
Building and launching digital projects, Privacy-respecting analytics (OptikAnalytics), No-code/low-code development, Consulting and business strategy, Digital product sales (Hiram's Digishop), GrapheneOS installation services (SwapMyOS)
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.5.1, Typed.js 2.0.11, Dorik (website builder platform), Cloudflare DNS and registrar services
Platforms
Dorik
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by URL and Cloudflare usage)
  • ClientTransferProhibited domain status
  • Use of privacy-respecting analytics (OptikAnalytics)
  • Honeypot field in contact form to prevent spam

Analytics and tracking

Services
OptikAnalytics, Aptimesi
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
OptikAnalytics pixel
Marketing tools
OptikAnalytics, Aptimesi analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal/business portfolio of a solopreneur and indie hacker.
  2. Multiple projects and ventures are showcased with clear branding.
  3. No privacy or cookie policies found, which is a compliance gap.
  4. Contact is only via a contact form; no direct email or phone found.
  5. Use of privacy-respecting analytics is a positive privacy indicator.
  6. No explicit security policies or incident response info published.
  7. No security headers detected in provided data; DNSSEC not enabled.
  8. Website is hosted and registered via Cloudflare, indicating good infrastructure.
  9. No signs of adult or questionable content; content is safe and professional.
Technical notes

Notes

The website is built using the Dorik website builder platform, leveraging jQuery 3.5.1 and Typed.js for dynamic text effects. Hosting and DNS services are provided by Cloudflare, ensuring reliable performance and security features like HTTPS. The site loads external fonts from fonts.cmsfly.com and uses CDN for static assets. Performance is moderate with good mobile optimization and SEO meta tags present. Accessibility is basic but could be improved. The contact form uses AJAX for submission with a honeypot anti-spam technique. No CMS beyond Dorik is detected. The technical stack is modern and appropriate for a small business portfolio site, with opportunities to enhance security and compliance features.
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

Reviews of this site

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