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

searxng.canine.tools scored 78/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 7 checks passed, 6 warnings, 1 critical issues across 14 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

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.

searxng.canine.tools Security Report — Grade C+ (78/100)

Q: 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.

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). Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

Q: Does searxng.canine.tools use HSTS?

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

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

Yes. Strengths: Certificate valid, 74 days remaining; Issued by Let's Encrypt; 12 certificates logged in CT.

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

No. Strengths: 2 nameservers configured (ed.ns.cloudflare.com, marjory.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.

C+

78/100

searxng.canine.tools

June 09, 2026 ·

1 Critical 0+ Warnings 7 Passed

AI Summary

searxng.canine.tools scored 78/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: DMARC / Email Security. Positive signals: MX Records & Mail Provider, TLS Configuration, HSTS Header all passed.

3 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

Better than 59% of 2681 companies scanned.

059th pct100

A+

A-

B+

B-

C+

C-

D+

D-

DMARC / Email Security

MTA-STS & TLS Reporting

DNS CAA Records

DNS Configuration

Security Headers

Cookie Security

security.txt (RFC 9116)

MX Records & Mail Provider

TLS Configuration

HSTS Header

Known Breaches

TLS Protocol Support

CVE Exposure

Certificate Hygiene

C+

searxng.canine.tools

78/100

0 of 1 fixed

All 1 critical issue marked as fixed

Re-scan to confirm and update your score.

Set up email authentication (DKIM)

DMARC / Email Security

1–2 days

Without email authentication, anyone can send emails that appear to come from searxng.canine.tools. This is the most common vector for phishing attacks targeting employees and customers. DKIM is not configured.

NIST CSFPR.AC-7

Email authentication is a required access control

ISO 27001A.13.2.1

Information transfer policies require email security controls

HIPAA§164.312(e)

Transmission security for electronic PHI

How to fix this

1Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)

2Configure DKIM signing with your email provider and publish the public key in DNS

3Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]

4Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject

At a glance

Full data from this scan

TLS Version

TLSv1.3

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

DMARC Policy

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). Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

SPF Record

Present

v=spf1 include:_spf.protonmail.ch -all

Security Headers

5/5 present

All headers configured.

HSTS

Enabled

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

SSL Certificate

Valid

Strengths: Certificate valid, 74 days remaining; Issued by Let's Encrypt; 12 certificates logged in CT.

DNSSEC

Not enabled

Strengths: 2 nameservers configured (ed.ns.cloudflare.com, marjory.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.

Similar companies

Other domains with comparable security profiles.