Is licensetom.com safe to use as a vendor?

licensetom.com scored 70/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 6 checks passed, 5 warnings, 3 critical issues across 14 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

Does licensetom.com have security headers configured?

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

licensetom.com Security Report — Grade C- (70/100)

Q: What TLS version does licensetom.com use?

licensetom.com 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 licensetom.com have DMARC configured?

Yes. licensetom.com's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; SPF soft-fail (~all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: default). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua) — policy violations won't be reported.

Q: Does licensetom.com have SPF configured?

Yes. SPF record: v=spf1 +a +mx include:licensetom.com.spf.auto.dnssmarthost.net ~all

Q: Does licensetom.com use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

Q: Is licensetom.com's SSL certificate valid?

Yes. Strengths: Certificate valid, 86 days remaining; Issued by Let's Encrypt. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

Q: Does licensetom.com have DNSSEC enabled?

No. Strengths: 2 nameservers configured (ns2.siteground.net, ns1.siteground.net); SOA record present and MNAME consistent with NS set; 3 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (siteground.net) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

C- 70/100

licensetom.com

July 04, 2026 ·

1+ Warnings 6 Passed

Better than 42% of 2706 companies scanned.

042th pct100

A+

A-

B+

B-

C+

C-

D+

D-

HSTS Header

Security Headers

Cookie Security

MTA-STS & TLS Reporting

DNS CAA Records

DNS Configuration

DMARC / Email Security

security.txt (RFC 9116)

C-

licensetom.com

70/100

Strengthen email authentication configuration

DMARC / Email Security

2–4 hours

Email authentication is partially configured for licensetom.com 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.licensetom.com

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: DMARC pct=100 — policy applies to all mail; SPF soft-fail (~all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: default). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua) — policy violations won't be reported.

SPF Record

Present

v=spf1 +a +mx include:licensetom.com.spf.auto.dnssmarthost.net ~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. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

SSL Certificate

Valid

Strengths: Certificate valid, 86 days remaining; Issued by Let's Encrypt. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

DNSSEC

Not enabled

Strengths: 2 nameservers configured (ns2.siteground.net, ns1.siteground.net); SOA record present and MNAME consistent with NS set; 3 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (siteground.net) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Similar companies