Is focal.systems safe to use as a vendor?

focal.systems scored 70/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 4 checks passed, 2 warnings, 2 critical issues across 8 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

Does focal.systems have SPF configured?

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

Does focal.systems have security headers configured?

focal.systems has 0 of 5 recommended security headers. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

focal.systems Security Report — Grade C- (70/100)

Q: What TLS version does focal.systems use?

focal.systems uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Q: Does focal.systems have DMARC configured?

Yes. focal.systems's DMARC policy is set to 'none'. SPF record: yes. Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Q: Does focal.systems use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Q: Is focal.systems's SSL certificate valid?

Yes. Strengths: Certificate valid, 38 days remaining; Issued by Google Trust Services.

Q: Does focal.systems have DNSSEC enabled?

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

C- 70/100

focal.systems

February 18, 2026 ·

1+ Warnings 4 Passed

AI Summary

focal.systems scored 70/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: HSTS Header, Security Headers. Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.

4 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 42% of 2692 companies scanned.

042th pct100

A+

A-

B+

B-

C+

C-

D+

D-

C-

focal.systems

70/100

Enable HSTS (HTTP Strict Transport Security)

< 1 hour

The HSTS header is missing on focal.systems. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.

PCI-DSS 4.0Req 6.4.1

Required application security controls

NIST 800-53SC-8

Transmission confidentiality and integrity

How to fix this

1Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2Verify all subdomains support HTTPS before adding includeSubDomains

3Test with: curl -sI https://focal.systems | grep -i strict

4Submit to hstspreload.org after confirming the header is correct

At a glance

Full data from this 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=none

Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

SPF Record

Present

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

Security Headers

0/5 present

Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy

HSTS

Not enabled

Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

SSL Certificate

Valid

Strengths: Certificate valid, 38 days remaining; Issued by Google Trust Services.

DNSSEC

Not enabled

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

Similar companies