Is searxng.canine.tools safe to use as a vendor?

searxng.canine.tools scored 82/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 8 checks passed, 7 warnings, 0 critical issues across 15 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does searxng.canine.tools use?

searxng.canine.tools 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 searxng.canine.tools have SPF configured?

Yes. SPF record: v=spf1 include:_spf.protonmail.ch -all

Does searxng.canine.tools have security headers configured?

searxng.canine.tools has 5 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. All recommended headers present.

Does searxng.canine.tools use HSTS?

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

Has searxng.canine.tools been involved in a data breach?

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

Does searxng.canine.tools have known CVE vulnerabilities?

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

Is searxng.canine.tools's SSL certificate valid?

Yes. Strengths: Certificate valid, 70 days remaining; Issued by Let's Encrypt.

searxng.canine.tools Security Report — Grade B- (82/100)

Q: Does searxng.canine.tools have DMARC configured?

Yes. searxng.canine.tools's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: protonmail, protonmail2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Q: Does searxng.canine.tools have DNSSEC enabled?

No. Strengths: 2 nameservers configured (marjory.ns.cloudflare.com, ed.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 2 MX record(s) present; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain.

B-

Trust rating

Good · 82/100

Procurement snapshot

No critical findings. The 7 remaining items are configuration gaps, not architectural problems.

Strengths

TLS Configuration

MX Records & Mail Provider

HSTS Header

Known Breaches

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 1–2 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned June 13, 2026

Score

100 75 50 25 0

B-

searxng.canine.tools

82/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

7 items need attention

8 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for searxng.canine.tools is partly set up, but there are gaps: your DMARC policy is set to monitor-only, so nothing actually gets blocked yet. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Change your DMARC policy from "none" to "quarantine" in your domain's DNS settings (check with whoever manages your website or domain registration) — this moves suspicious mail to spam instead of just watching it happen. Your current record with just that change:

v=DMARC1; p=quarantine; rua=mailto:[email protected]

2Double-check it's live: search "dmarc record checker" and enter searxng.canine.tools.

Email authentication guide

Report unlocked.

View all 8 passed checks

TLS Configuration

MX Records & Mail Provider

HSTS Header

Known Breaches

TLS Protocol Support

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded B

794 companies · LynxRadar ranking

High Priority

p=none

Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: protonmail, protonmail2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

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

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 2 nameservers configured (marjory.ns.cloudflare.com, ed.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 2 MX record(s) present; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Warn

Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have SameSite attribute. Issues: 2/2 cookie(s) missing HttpOnly flag (techaro.lol-anubis-auth, techaro.lol-anubis-cookie-verification).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Best Practice

Warn

Strengths: CAA records configured at canine.tools (10 record(s)); Authorised CAs: comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com; Wildcard CAs: ssl.com, comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes. Issues: No iodef record — CA violations won't be reported to the domain owner.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

5/5 present

All headers configured.

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: ★☆☆☆☆