Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
lynxradar.com scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.
1 action item identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How lynxradar.com compares
Grade distribution across 2378 companies we've scanned. lynxradar.com scores better than 92% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
lynxradar.com — Grade A- (92/100)
2378 companies scanned
Security checks
Each check inspects a different part of lynxradar.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
Strengths: CAA records configured (11 record(s)); Authorized 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.
security.txt (RFC 9116)
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.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
MX Records & Mail Provider
Strengths: Mail handled by route3.mx.cloudflare.net; 3 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
HSTS Header
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. preload present.
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
DNS Configuration
Strengths: 2 nameservers configured (camilo.ns.cloudflare.com., sue.ns.cloudflare.com.); 3 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 80 days remaining; Issued by Google Trust Services; 10 certificates logged in CT; Certificates from 2 CAs: Google Trust Services, Let's Encrypt.
Recommended actions
1 item
Steps to improve lynxradar.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for lynxradar.com but has gaps. Actions needed: configure DKIM. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.lynxradar.com
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all). Issues: 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.mx.cloudflare.net ~all
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. preload present.
SSL Certificate
Valid
Strengths: Certificate valid, 80 days remaining; Issued by Google Trust Services; 10 certificates logged in CT; Certificates from 2 CAs: Google Trust Services, Let's Encrypt.
DNSSEC
Enabled
Strengths: 2 nameservers configured (camilo.ns.cloudflare.com., sue.ns.cloudflare.com.); 3 MX records present; DNSSEC enabled; Zone transfers properly restricted.