Is nonexistent-domain-test-xyz.example safe to use as a vendor?

nonexistent-domain-test-xyz.example scored 61/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 3 checks passed, 5 warnings, 1 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does nonexistent-domain-test-xyz.example use?

TLS configuration for nonexistent-domain-test-xyz.example could not be determined. Could not complete TLS handshake with nonexistent-domain-test-xyz.example:443 — [Errno 8] nodename nor servname provided, or not known

Does nonexistent-domain-test-xyz.example have SPF configured?

No. No SPF record found for nonexistent-domain-test-xyz.example.

Does nonexistent-domain-test-xyz.example have security headers configured?

nonexistent-domain-test-xyz.example has 0 of 0 recommended security headers. All recommended headers present.

Does nonexistent-domain-test-xyz.example use HSTS?

No. Could not fetch https://nonexistent-domain-test-xyz.example — connection failed or timed out.

Has nonexistent-domain-test-xyz.example been involved in a data breach?

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

Does nonexistent-domain-test-xyz.example 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.

Is nonexistent-domain-test-xyz.example's SSL certificate valid?

Issues detected. Note: Could not retrieve the live certificate — see the TLS check.

nonexistent-domain-test-xyz.example Security Report — Grade D- (61/100)

Q: Does nonexistent-domain-test-xyz.example have DMARC configured?

No. nonexistent-domain-test-xyz.example's DMARC policy is set to 'none'. SPF record: no. Issues: No DMARC record found — email spoofing is not prevented; No SPF record found. Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

Q: Does nonexistent-domain-test-xyz.example have DNSSEC enabled?

No. Issues: No NS records found (unusual — possible DNS misconfiguration); SOA record missing — possible lame delegation or DNS misconfiguration; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning); No A or AAAA records found — domain does not resolve to an IP address.

D-

Trust rating

Weak · 61/100

Procurement snapshot

1 critical finding identified — these point to architectural gaps, not just configuration tweaks.

Strengths

MX Records & Mail Provider

Known Breaches

CVE Exposure

Questions to ask

Confirm email authentication (SPF/DKIM/DMARC) rollout plans

Estimated remediation effort: 2–6 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 11, 2026

Score

100 75 50 25 0

D-

nonexistent-domain-test-xyz.example

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

5 items need attention

3 passed

0 of 1 fixed

All 1 critical issue marked as fixed

Re-scan to confirm and update your score.

Turn on email authentication (SPF, DKIM, DMARC)

DMARC / Email Security

1–2 days Critical

This exposes customers, partners, and employees to phishing attacks that impersonate your brand. Right now, anyone can send an email that looks like it came from [email protected] — no password or hack required. This is how the vast majority of phishing scams that impersonate a company work, and it can damage your reputation with customers even though your systems were never touched. Missing: DMARC, SPF.

NIST SP 800-177r1§4

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

ISO 27001:2022A.5.14

Information transfer controls cover email

CISA BOD 18-01DMARC

Requires DMARC p=reject on US federal email domains

How to fix this

1Add an SPF record in your domain's DNS settings (check with whoever manages your website or domain registration). This is a line of text that tells other mail servers which servers are allowed to send email as you.

v=spf1 include:_spf.google.com ~all

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

2Not sure which value to use? Search "[your email provider] SPF record" (e.g. "Google Workspace SPF record") — every provider publishes the exact line to use.

3If DKIM signing isn't on yet (we can't confirm it from outside): Turn on DKIM signing — look for "DKIM" under your email provider's admin/security settings. It gives you a record to add in your domain's DNS settings (check with whoever manages your website or domain registration).

4Add a DMARC record in your domain's DNS settings (check with whoever manages your website or domain registration). This tells receiving mail servers what to do with messages that fail SPF and DKIM checks (start on "quarantine" — send to spam — rather than "reject", so nothing legitimate gets blocked while you're testing).

5After 2–4 weeks, check the DMARC reports for anything legitimate that got flagged, then tighten the policy from quarantine to reject.

Email authentication guide

Report unlocked.

View all 3 passed checks

MX Records & Mail Provider

Known Breaches

CVE Exposure

Couldn't check: TLS Protocol Support, TLS Configuration, Malware / Phishing Blocklist, HSTS Header, Security Headers, Cookie Security, Certificate Hygiene — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so these aren't counted in the score.

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 D

832 companies · LynxRadar ranking

Blocking Issues

Not configured

Issues: No DMARC record found — email spoofing is not prevented; No SPF record found. Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

Likelihood: ★★★★★

Impact: ★★★★☆

Missing

No SPF record found.

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

Issues: No NS records found (unusual — possible DNS misconfiguration); SOA record missing — possible lame delegation or DNS misconfiguration; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning); No A or AAAA records found — domain does not resolve to an IP address.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

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

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

Could not load nonexistent-domain-test-xyz.example's homepage to detect its e-commerce platform, payment processor, or CDN.

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