Skip to main content

Security report for typeof.net

Belleve Invis · Technology · N/a

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

Security score

62/100

Risk levelMedium

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

Typeof.net is a personal website operated by Renzhi Li (aka be5invis), focusing on typography, type theory, and digital typeface design, notably the Iosevka programming font. The site serves a niche audience of typography enthusiasts and programmers interested in font design and text processing. The business model is that of an individual content creator and font designer, with a long-standing domain registration since 2009, indicating sustained activity and credibility in the niche. Technically, the website is built using the Hexo static site generator and hosted on GitHub Pages, leveraging modern web fonts and CSS libraries such as Font Awesome and Iosevka fonts. The site is performant and mobile-optimized with a clean, consistent design, though accessibility and SEO optimizations are basic. No advanced analytics or tracking technologies are detected, reflecting a privacy-conscious approach. From a security perspective, the site lacks several best practices: no DNSSEC, no security headers, and no published privacy or cookie policies. The domain is registered without privacy protection, consistent with the personal nature of the site. No contact or incident response information is provided, limiting transparency. Overall, the security posture is moderate but could be improved with standard web security enhancements. The overall risk is low given the non-commercial, informational nature of the site, but improvements in privacy compliance and security hardening are recommended to enhance trust and protect visitors. Strategic recommendations include enabling DNSSEC, adding security headers, publishing privacy and cookie policies, and providing contact information for security incidents.

Scanned

NIS2 and GDPR posture

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

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 typeof.net

This scan found 26 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
72
Security headers
15
Email security
55
DNS health
80
Network security
100
GDPR outside view
50
Average
62

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention typeof.net, from OffSeq Breach.

No leaked records found

Breach holds no records for typeof.net right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Typeof.net operates as a personal brand and content platform for Renzhi Li, a typography expert and font creator. The site targets a specialized community interested in programming fonts and digital typography. The business model is individual-driven, focusing on content creation and font distribution rather than commercial transactions. The domain's long history since 2009 supports credibility and sustained engagement. The site is hosted on GitHub Pages, indicating low operational costs and a lean infrastructure. There are no visible partnerships or subsidiaries. The lack of commercial elements and contact details suggests a focus on personal branding and community contribution rather than direct monetization.

Security posture

The website demonstrates a basic security posture with no advanced protections detected. The absence of DNSSEC and security headers such as Content-Security-Policy or Strict-Transport-Security reduces resilience against DNS spoofing and common web attacks. The lack of HTTPS enforcement details is a concern, though GitHub Pages typically provides HTTPS by default. No privacy or cookie policies are published, which is a compliance gap under GDPR and similar regulations. No incident response or security contact information is available, limiting the ability to report or respond to security issues. Overall, the site is low risk due to its informational nature but would benefit from standard security improvements to protect users and enhance trust.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and enforce HTTPS with HSTS to secure data in transit.
  3. Add security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user transparency.
  5. Provide clear contact information including security incident response contacts to facilitate communication.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Belleve Invis
Description
Personal website of Renzhi Li (aka be5invis) focusing on typography, type theory, text processing, and digital typography for global languages. Creator of the Iosevka programming typeface.
Key services
Typeface creation (Iosevka), Typography writings and research
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, Font Awesome, Iosevka font, Source Serif 4 font, Math Symbol font
Frameworks
Hexo
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a personal portfolio and blog focused on typography and typeface design.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No security policies or incident response information available.
  5. No advertising or tracking technologies detected.
  6. Site is hosted on GitHub Pages and uses Hexo static site generator.
  7. WHOIS data shows domain is registered since 2009 with no privacy protection.
  8. No security headers or DNSSEC enabled, indicating room for security improvements.
Technical notes

Notes

The website uses a modern static site generator (Hexo) and is hosted on GitHub Pages, ensuring good performance and uptime. The tech stack includes modern web fonts and CSS libraries, contributing to a visually appealing and responsive design. However, accessibility features are basic and SEO optimizations are minimal. No analytics or tracking scripts are present, which aligns with privacy-conscious design but limits marketing insights. The absence of security headers and DNSSEC indicates technical debt in security hardening. Overall, the infrastructure is simple, stable, and efficient but could be enhanced with additional 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 typeof.net. 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 typeof.net.

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.