Is dmarcly.com safe to use as a vendor?

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

Does dmarcly.com have security headers configured?

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

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

Q: What TLS version does dmarcly.com use?

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

Yes. dmarcly.com's DMARC policy is set to 'quarantine'. SPF record: yes. Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: s1, s2, dkim, mail). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Q: Does dmarcly.com have SPF configured?

Yes. SPF record: v=spf1 include:_u.dmarcly.com._spf.dmarcly.com include:servers.mcsv.net -all

Q: Does dmarcly.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 dmarcly.com's SSL certificate valid?

Yes. Strengths: Certificate valid, 51 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

Q: Does dmarcly.com have DNSSEC enabled?

No. Strengths: 2 nameservers configured (jule.ns.cloudflare.com, dean.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 3 A record(s), 3 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — 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

dmarcly.com

June 14, 2026 ·

1+ Warnings 6 Passed

Better than 42% of 2690 companies scanned.

042th pct100

A+

A-

B+

B-

C+

C-

D+

D-

HSTS Header

Security Headers

MX Records & Mail Provider

DNS Configuration

DNS CAA Records

MTA-STS & TLS Reporting

security.txt (RFC 9116)

DMARC / Email Security

C-

dmarcly.com

70/100

Enable HSTS (HTTP Strict Transport Security)

HSTS Header

< 1 hour

The HSTS header is missing on dmarcly.com. 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://dmarcly.com | 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=quarantine

Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: s1, s2, dkim, mail). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

SPF Record

Present

v=spf1 include:_u.dmarcly.com._spf.dmarcly.com include:servers.mcsv.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, 51 days remaining; Issued by Google Trust Services. 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 (jule.ns.cloudflare.com, dean.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 3 A record(s), 3 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — 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