Is dockhand.srv1.shadowadmins.com safe to use as a vendor?

dockhand.srv1.shadowadmins.com scored 52/100 on LynxRadar's security posture assessment. The domain has significant security gaps that should be addressed. 4 checks passed, 6 warnings, 0 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does dockhand.srv1.shadowadmins.com use?

TLS configuration for dockhand.srv1.shadowadmins.com could not be determined. Could not complete TLS handshake with dockhand.srv1.shadowadmins.com:443 — [Errno 101] Network is unreachable

Does dockhand.srv1.shadowadmins.com have DMARC configured?

Yes. dockhand.srv1.shadowadmins.com's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; DKIM alignment: strict (adkim=s); SPF alignment: strict (aspf=s); Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: dkim).

Does dockhand.srv1.shadowadmins.com have SPF configured?

Yes. SPF record found: v=spf1 a:smtp.cryptomailbox.eu a:smtp-bkp01.cryptomailbox.eu ip4:78.47.206.88 ip...

Does dockhand.srv1.shadowadmins.com have security headers configured?

dockhand.srv1.shadowadmins.com has 0 of 0 recommended security headers. All recommended headers present.

Does dockhand.srv1.shadowadmins.com use HSTS?

No. Could not fetch https://dockhand.srv1.shadowadmins.com — connection failed or timed out.

Has dockhand.srv1.shadowadmins.com been involved in a data breach?

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

Does dockhand.srv1.shadowadmins.com have known CVE vulnerabilities?

No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.

dockhand.srv1.shadowadmins.com Security Report — Grade F (52/100)

Q: Is dockhand.srv1.shadowadmins.com's SSL certificate valid?

Issues detected. Strengths: 6 certificates logged in CT. Issues: Could not retrieve certificate details.

Q: Does dockhand.srv1.shadowadmins.com have DNSSEC enabled?

No. Strengths: 2 nameservers configured (ns2.desec.org, ns1.desec.io); NS records span 2 providers (desec.org, desec.io) — genuine redundancy; 1 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. Issues: SOA MNAME 'get.desec.io' not listed in NS records — possible lame delegation or stale primary nameserver reference; No A or AAAA records found — domain does not resolve to an IP address.

Trust rating

Fail · 52/100

Procurement snapshot

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

Strengths

DNS CAA Records

DMARC / Email Security

Known Breaches

CVE Exposure

Questions to ask

Confirm backup mail server configuration

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 July 13, 2026

Score

100 75 50 25 0

dockhand.srv1.shadowadmins.com

52/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

CCPA

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

4 items need attention

4 passed

Add a backup mail server record

MX Records & Mail Provider

30 minutes

This is a business-continuity gap — a single point of failure for all inbound email. dockhand.srv1.shadowadmins.com only has one mail server listed to receive email. If that single server has an outage, incoming email has nowhere else to go — it gets delayed or bounced back to the sender until the server recovers.

How to fix this

1Ask your email provider whether they publish a second/backup mail server address (most do).

2Add it as a second MX record in your domain's DNS settings (check with whoever manages your website or domain registration), with a higher priority number than your main one (higher number = lower priority = used only as backup).

3Confirm it worked: search "mx record checker" and enter dockhand.srv1.shadowadmins.com — you should see 2 or more records.

Report unlocked.

View all 4 passed checks

DNS CAA Records

DMARC / Email Security

Known Breaches

CVE Exposure

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.dockhand.srv1.shadowadmins.com ↗

Security page

dockhand.srv1.shadowadmins.com/security ↗

dockhand.srv1.shadowadmins.com/privacy ↗

DPA (Data Processing Agreement)

dockhand.srv1.shadowadmins.com/dpa ↗

Updated recently

Subprocessors List

dockhand.srv1.shadowadmins.com/policies/subprocessors ↗

Similar companies

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

Medium Priority

Warn

Strengths: Mail handled by smtp.cryptomailbox.eu; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆

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 (ns2.desec.org, ns1.desec.io); NS records span 2 providers (desec.org, desec.io) — genuine redundancy; 1 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. Issues: SOA MNAME 'get.desec.io' not listed in NS records — possible lame delegation or stale primary nameserver reference; No A or AAAA records found — domain does not resolve to an IP address.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Warn

Could not load dockhand.srv1.shadowadmins.com's homepage to detect its e-commerce platform, payment processor, or CDN.

Best Practice

Issues

Strengths: 6 certificates logged in CT. Issues: Could not retrieve certificate details.

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