Skip to main content

Security report for micro.blog

Contact Privacy Inc. Customer 0146539264 · Technology · Canada

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

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

Micro.blog is a niche technology platform founded in 2017 that offers users an easy way to blog on their own domain names, supporting short posts, essays, photo blogs, and email newsletters. It emphasizes community engagement and cross-posting to other social networks, positioning itself as a user-centric alternative to large social media silos. The platform targets bloggers and content creators seeking more control over their online presence. Technically, the website uses standard modern web technologies (HTML5, CSS3, JavaScript) and is hosted with DNSimple, though DNSSEC is not enabled. The site is mobile optimized with good design and navigation, but lacks advanced accessibility features and some SEO enhancements. Security posture is moderate; domain registration is privacy protected but stable and consistent with the business history. However, the site lacks published privacy, cookie, and security policies, and no security headers were detected, indicating room for improvement in compliance and security transparency. Overall, the website is professional and trustworthy with a good user experience but could enhance its security and privacy compliance to better meet industry standards.

Scanned

This is an earlier scan of micro.blog. View the latest report

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

6 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 micro.blog

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
100
Security headers
15
Email security
70
DNS health
75
Network security
100
GDPR outside view
50
Average
68

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

Micro.blog operates in the technology sector as a small-sized company focused on microblogging and indie blogging services. Its business model is subscription-based, offering blog hosting, community features, and cross-posting capabilities. The company leverages a partnership with micro.one, another microblogging-related domain. The founder, Manton Reece, is publicly identified with a personal website and authored a book on indie microblogging, adding credibility. The platform appeals to independent bloggers and creators who value control and community over large social networks. Revenue streams likely include subscription fees and possibly related services. The company maintains a lean operation with no visible subsidiaries or parent company. The website content and branding are consistent and professional, supporting a high trust level among its target audience.

Security posture

The current security posture of Micro.blog is moderate. The domain is registered with privacy protection, which is justified for a small technology business. The domain status flags clientTransferProhibited and clientUpdateProhibited add protection against unauthorized transfers or updates. However, the absence of DNSSEC reduces DNS security. No security headers such as Content-Security-Policy, X-Frame-Options, or Strict-Transport-Security were detected, which are recommended best practices. The website lacks published security policies or incident response contacts, limiting transparency and preparedness communication. No vulnerabilities or exposed sensitive data were found in the provided HTML content. The site uses HTTPS (implied by URL) but SSL configuration details are unknown. Overall, the security posture is adequate but could be significantly improved by implementing security headers, enabling DNSSEC, and publishing security and privacy policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve browser security.
  4. Publish a security policy and incident response contact information to improve transparency and readiness.
  5. Consider adding accessibility improvements and SEO enhancements to improve user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Contact Privacy Inc. Customer 0146539264
Description
Micro.blog provides easy blogging at your own domain name for short posts, full essays, photo blogs, and email newsletters, with a friendly community, cross-posting to other networks, and more.
Key services
blog hosting, cross-posting to social networks, community engagement, email newsletters
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • Domain status clientTransferProhibited and clientUpdateProhibited

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
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No explicit privacy, cookie, or terms of service policies found on homepage.
  3. Contact information limited to a support email in footer.
  4. No phone numbers or physical addresses provided.
  5. No security or incident response policies published.
  6. Website uses modern HTML5 and JavaScript with moderate performance.
  7. No analytics or advertising scripts detected in provided HTML.
  8. Domain uses DNSimple nameservers but DNSSEC is not enabled.
  9. Website branding and content are consistent and professional.
  10. No adult or questionable content detected.
Technical notes

Notes

The website uses a clean and modern HTML5 structure with CSS and JavaScript for interactivity and styling. It loads images and stylesheets efficiently and includes basic scripts for UI enhancements such as background image loading and scroll-based header effects. The hosting provider appears to be DNSimple based on the nameservers, a reputable DNS and hosting service. The site is mobile optimized with responsive meta tags and good navigation clarity. No CMS or advanced frameworks were detected in the provided HTML. Performance is moderate with no obvious blocking scripts or heavy resources. No analytics or advertising scripts were found, indicating minimal tracking. The lack of DNSSEC and security headers represents technical debt and security risk. Overall, the technical implementation is solid but could benefit from modern security and privacy enhancements.
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. 68/100Medium31 findingsView report
Reviews of this site

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

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.