Is manicule.dev safe to use as a vendor?

manicule.dev scored 80/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 5 warnings, 1 critical issues across 15 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does manicule.dev use?

manicule.dev uses TLSv1.3 with TLS_AES_128_GCM_SHA256. TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does manicule.dev have SPF configured?

Yes. SPF record: v=spf1 include:_spf.mail.hostinger.com include:_spf.google.com ~all

Does manicule.dev have security headers configured?

manicule.dev has 0 of 5 recommended security headers. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

Does manicule.dev use HSTS?

Yes. HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.

Has manicule.dev been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does manicule.dev have known CVE vulnerabilities?

Detected technologies: Vercel. (Vercel detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

Is manicule.dev's SSL certificate valid?

Yes. Strengths: Certificate valid, 41 days remaining; Issued by Let's Encrypt; 24 certificates logged in CT; Certificates from 2 CAs: Let's Encrypt, Sectigo Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

manicule.dev Security Report — Grade B- (80/100)

Q: Does manicule.dev have DMARC configured?

Yes. manicule.dev's DMARC policy is set to 'none'. SPF record: yes. Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).

Q: Does manicule.dev have DNSSEC enabled?

No. Strengths: 2 nameservers configured (tom.ns.cloudflare.com., walk.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

B-

Pass · 80/100

Shows significant security gaps that need urgent attention. Positive signals: TLS Protocol Support, TLS Configuration, and HSTS Header all passed. 6 action items identified, including 0 critical. The issues point to real architectural gaps, not just configuration tweaks. A focused remediation effort of 1–2 days could address all findings.

Trust Score Trend

→ No change 1 scan · Last scanned March 29, 2026

Your rating Industry average

Score

100 75 50 25 0

B-

manicule.dev

80/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Pro subscribers only

ISO 27001

Certificate not on file

3rd party · accredited body

Pro subscribers only

GDPR

DPA not on file

Self-reported

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

6 items need attention

9 passed

Add 5 missing security headers

Security Headers

1–2 hours

This leaves visitors exposed to attacks like clickjacking and content-type sniffing. manicule.dev is missing 5 of the 5 security headers browsers use to protect visitors — for example, one stops your site being loaded inside a hidden frame on another site to trick people into clicking things (clickjacking). These are settings, not code changes, so they're usually quick to add.

PCI-DSS 4.0Req 6.4.1

Security headers are required application controls

OWASPSecure Headers

Recommended baseline for web applications

How to fix this

1Add these headers exactly as shown. You're using Vercel in front of this site — add it there, see https://vercel.com/docs/headers/response-headers.

Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

Referrer-Policy: strict-origin-when-cross-origin

Permissions-Policy: camera=(), microphone=(), geolocation=()

2Confirm it worked: search "http header checker" and enter manicule.dev — check the headers below in the response.

Security headers guide

Report unlocked.

View all 9 passed checks

TLS Protocol Support

TLS Configuration

HSTS Header

Known Breaches

Cookie Security

MX Records & Mail Provider

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.manicule.dev ↗

Security page

manicule.dev/security ↗

manicule.dev/privacy ↗

DPA (Data Processing Agreement)

manicule.dev/dpa ↗

Updated recently

Subprocessors List

manicule.dev/policies/subprocessors ↗

Tech Stack Detected

Subprocessors

Vercel

Similar companies in B2B SaaS / Software

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Blocking Issues

0/5 present

Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 2 nameservers configured (tom.ns.cloudflare.com., walk.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

p=none

Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆