Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
ltse.com scored 98/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, Known Breaches, HSTS Header 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 ltse.com compares
Grade distribution across 2378 companies we've scanned. ltse.com scores better than 97% 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
ltse.com — Grade A+ (98/100)
2378 companies scanned
Security checks
Each check inspects a different part of ltse.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 4 nameservers configured (ns4.dnsimple.com., ns1.dnsimple.com., ns2.dnsimple.com., ns3.dnsimple.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
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.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1, mandrill).
Certificate Hygiene
Strengths: Certificate valid, 47 days remaining; Issued by Google Trust Services.
Recommended actions
1 item
Steps to improve ltse.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for ltse.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec ltse.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 hard-fail (-all); DKIM configured (selectors: google, k1, mandrill).
SPF Record
Present
v=spf1 a include:_spf.google.com include:helpscoutemail.com include:spf.mandrillapp.com include:serv
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 47 days remaining; Issued by Google Trust Services.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns4.dnsimple.com., ns1.dnsimple.com., ns2.dnsimple.com., ns3.dnsimple.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.