Is secured.community safe to use as a vendor?

secured.community scored 45/100 on LynxRadar's security posture assessment. The domain has significant security gaps that should be addressed. 2 checks passed, 3 warnings, 0 critical issues across 8 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does secured.community use?

TLS configuration for secured.community could not be determined. Could not complete TLS handshake with secured.community:443 — [Errno -5] No address associated with hostname

Does secured.community have SPF configured?

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

Does secured.community have security headers configured?

secured.community has 0 of 0 recommended security headers. All recommended headers present.

Is secured.community's SSL certificate valid?

Issues detected. Issues: Could not retrieve certificate details.

secured.community Security Report — Grade F (45/100)

Q: Does secured.community have DMARC configured?

No. secured.community's DMARC policy is set to 'none'. SPF record: yes. Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.

Q: Does secured.community use HSTS?

No. Could not fetch https://secured.community — connection failed or timed out.

Q: Does secured.community have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-cloud-e1.googledomains.com., ns-cloud-e4.googledomains.com., ns-cloud-e3.googledomains.com., ns-cloud-e2.googledomains.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

F 45/100

secured.community

February 18, 2026 ·

1+ Warnings 2 Passed

AI Summary

secured.community scored 45/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.

Positive signals: Known Breaches, CVE Exposure all passed.

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

Better than 11% of 2692 companies scanned.

011th pct100

A+

A-

B+

B-

C+

C-

D+

D-

secured.community

45/100

Strengthen email authentication configuration

2–4 hours

Email authentication is partially configured for secured.community but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.

NIST CSFPR.AC-7

Email authentication is a required access control

How to fix this

1Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)

2Verify with: nslookup -type=txt _dmarc.secured.community

At a glance

Full data from this scan

TLS Version

Issues detected

Could not complete TLS handshake with secured.community:443 — [Errno -5] No address associated with hostname

DMARC Policy

Not configured

Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.

SPF Record

Present

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

Security Headers

0/0 present

All headers configured.

HSTS

Not enabled

Could not fetch https://secured.community — connection failed or timed out.

SSL Certificate

Issues

Issues: Could not retrieve certificate details.

DNSSEC

Not enabled

Strengths: 4 nameservers configured (ns-cloud-e1.googledomains.com., ns-cloud-e4.googledomains.com., ns-cloud-e3.googledomains.com., ns-cloud-e2.googledomains.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Similar companies