Skip to main content

Security report for microlink.io

Microlink HQ · Technology · N/a

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

81/100

Risk levelLow

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

Microlink is a technology company providing a high-level API service that enables businesses and developers to control headless browsers for web scraping, metadata extraction, screenshot generation, and PDF creation. The company positions itself as a developer-first, scalable browser-as-a-service platform with a global CDN infrastructure and built-in caching to optimize performance and reliability. Their business model includes tiered pricing plans with a free tier, pro, and enterprise options, targeting developers and businesses requiring automated web data extraction and processing. Technically, the website is built using modern web technologies including React and Gatsby, hosted on Vercel and leveraging Cloudflare's CDN for global distribution. The site demonstrates excellent performance, mobile optimization, and SEO practices. Payment processing is securely handled via Stripe, and analytics are collected minimally through Vercel Insights. The site lacks a cookie consent mechanism but maintains good privacy compliance with a comprehensive privacy policy. From a security perspective, the site enforces HTTPS, uses clientTransferProhibited domain status, and isolates requests to prevent shared browser sessions. However, it lacks DNSSEC and explicit security headers, and does not publish a dedicated security policy or incident response contacts. The domain registration is privacy protected but consistent with a legitimate tech startup, with no suspicious patterns detected. Overall, Microlink presents a professional, trustworthy, and technically mature online presence with minor areas for improvement in security transparency and privacy mechanisms. The risk profile is low, with recommendations to enhance DNS security, implement security headers, and provide clearer incident response information.

Scanned

NIS2 and GDPR posture

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

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

This scan found 15 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
75
Security headers
75
Email security
85
DNS health
90
Network security
100
GDPR outside view
58
Average
81

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

Microlink operates in the technology sector, focusing on providing API-driven browser automation and web data extraction services. Its competitive advantages include a developer-first approach, open source components, and a scalable cloud infrastructure with a global CDN. Revenue streams are based on subscription plans with usage-based pricing. The target customers are developers and businesses needing reliable web scraping and metadata services. Growth indicators include a mature domain age, active GitHub presence, and a clear product roadmap. Partnerships with Stripe, Cloudflare, and Vercel support operational reliability and payment processing. The company maintains a transparent pricing model and offers a free tier to attract new users, facilitating market penetration and customer acquisition.

Security posture

Microlink demonstrates a moderate to high security maturity level with enforced HTTPS, domain transfer protection, and request isolation to prevent cross-request contamination. The absence of DNSSEC and security headers like CSP or HSTS represents an area for improvement. No exposed sensitive data or vulnerable libraries were detected in the website content. The lack of published incident response contacts or a security policy limits transparency and readiness perception. Compliance with GDPR is indicated by a comprehensive privacy policy. Overall, the security posture is solid but could benefit from enhanced DNS security, explicit security headers, and formalized incident response documentation to improve trust and resilience.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and publish security headers such as Content Security Policy (CSP), HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Create and publish a dedicated security policy and incident response contact information to enhance transparency and preparedness.
  4. Add a cookie consent mechanism if cookies or tracking technologies are used to comply with privacy regulations.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Microlink HQ
Description
Microlink is a fast, scalable, and reliable high-level API to control a headless browser built for businesses and developers. Proudly open source.
Key services
Logo (favicon) extraction, Screenshot generation, SDK for link previews, Performance insights powered by Lighthouse, Unified metadata extraction, PDF generation, Web scraping automation
Content quality
excellent
Branding
consistent

Technology

Stack
React, Gatsby, Cloudflare CDN, Stripe (payment processing)
Frameworks
Gatsby
Platforms
Cloudflare, Vercel
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited
  • Request isolation with no shared browsers between requests
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Vercel Insights
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Vercel Insights
Marketing tools
Mailchimp (email subscription form)
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and professional design
  2. Strong focus on developer tools and API services
  3. Clear pricing plans with free tier and enterprise options
  4. Good use of modern web technologies and CDN for performance
  5. Contact primarily via email; no phone or physical address found
  6. No explicit cookie consent mechanism detected
  7. No explicit security or incident response policies published
  8. WHOIS privacy protection is used but justified for this business type
Technical notes

Notes

The website is built on a modern React and Gatsby framework, ensuring fast loading times and excellent mobile responsiveness. Hosting on Vercel combined with Cloudflare CDN provides robust global distribution and performance optimization. The use of Stripe for payment processing ensures secure financial transactions. The site includes minimal tracking via Vercel Insights and uses Mailchimp for email subscriptions. The technical implementation is clean with valid HTML and CSS, good SEO metadata, and accessibility considerations. Opportunities exist to enhance security headers and DNS configurations to reduce technical risks and improve overall security posture.
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 microlink.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 microlink.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.