Is eliseai.com safe to use as a vendor?

eliseai.com scored 80/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 5 warnings, 1 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does eliseai.com use?

eliseai.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.

Does eliseai.com have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:45321630.spf03.hubspotemail.net include:m...

Does eliseai.com have security headers configured?

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

Does eliseai.com use HSTS?

Yes. HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.

Has eliseai.com been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does eliseai.com have known CVE vulnerabilities?

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.

Is eliseai.com's SSL certificate valid?

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

eliseai.com Security Report — Grade B- (80/100)

Q: Does eliseai.com have DMARC configured?

Yes. eliseai.com's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: google, s1, s2, resend). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Q: Does eliseai.com have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-1678.awsdns-17.co.uk, ns-975.awsdns-57.net, ns-1362.awsdns-42.org, ns-404.awsdns-50.com); NS records span 4 providers (co.uk, awsdns-57.net, awsdns-42.org, awsdns-50.com) — genuine redundancy; SOA record present and MNAME consistent with NS set; 5 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Featured in our Forbes AI 50 security study: see how eliseai.com compares with the other 49 →

B-

Trust rating

Good · 80/100

Procurement snapshot

0 critical findings identified — these point to architectural gaps, not just configuration tweaks.

Strengths

MX Records & Mail Provider

TLS Configuration

HSTS Header

TLS Protocol Support

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 2–4 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned September 28, 2026

Score

100 75 50 25 0

B-

eliseai.com

80/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

6 items need attention

9 passed

Add 5 missing security headers

Security Headers

1–2 hours High

This leaves visitors exposed to attacks like clickjacking and content-type sniffing. eliseai.com is missing 5 of the 5 security headers browsers use to protect visitors — for example, one stops your site being loaded inside a hidden frame on another site to trick people into clicking things (clickjacking). These are settings, not code changes, so they're usually quick to add.

PCI-DSS 4.0Req 6.4.1

Security headers are required application controls

OWASPSecure Headers

Recommended baseline for web applications

How to fix this

1Add these headers exactly as shown. You're using Cloudflare in front of this site — add it there, see https://developers.cloudflare.com/rules/transform/response-header-modification/create-dashboard/.

Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

Referrer-Policy: strict-origin-when-cross-origin

Permissions-Policy: camera=(), microphone=(), geolocation=()

2Confirm it worked: search "http header checker" and enter eliseai.com — the headers above should appear in the response.

Security headers guide

Report unlocked.

View all 9 passed checks

MX Records & Mail Provider

TLS Configuration

HSTS Header

TLS Protocol Support

Cookie Security

Subprocessors & Tech Stack

CVE Exposure

Known Breaches

Certificate Hygiene

Couldn't check: Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so this isn't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded B

791 companies · LynxRadar ranking

Blocking Issues

0/5 present

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

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

p=none

Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: google, s1, s2, resend). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 4 nameservers configured (ns-1678.awsdns-17.co.uk, ns-975.awsdns-57.net, ns-1362.awsdns-42.org, ns-404.awsdns-50.com); NS records span 4 providers (co.uk, awsdns-57.net, awsdns-42.org, awsdns-50.com) — genuine redundancy; SOA record present and MNAME consistent with NS set; 5 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

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.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆