verintefm.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

21risk

Low

Minor observations only.

0Critical

0High

1Medium

13Low

1Info

Collected 15 hours ago6.4sfrom cache

Headers—

unavailable

Certificate Transparency188
DNS resolution28
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs15
Registration
DNS posture4
Email authentication2
Certificate
Security headers
Archived URLs
Analysis15

noteFound 188 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 21 addresses; enriching the first 12.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.

Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: verintefm.com
52.4.252.153 (dbs.verintefm.com) reports nginx 1.28.2. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 52.4.252.153
dev.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.verintefm.com
staging.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: staging.verintefm.com
efm.staging.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: efm.staging.verintefm.com
www.staging.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.staging.verintefm.com
tabeast-test.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: tabeast-test.verintefm.com
tabeast-testing.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: tabeast-testing.verintefm.com
test-efmpreview.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: test-efmpreview.verintefm.com
secscansrv-staging.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: secscansrv-staging.verintefm.com
sandbox.healthspring.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: sandbox.healthspring.verintefm.com
www.secscansrv-staging.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.secscansrv-staging.verintefm.com
www.sandbox.healthspring.verintefm.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.sandbox.healthspring.verintefm.com
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: verintefm.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: verintefm.com

✓Receives mail via 27 servers
mx1.hc2746-61.iphmx.com mx2.hc2746-61.iphmx.com smtp.verintefm.com smtp02.verintefm.com+23
✓SPFends in -all
v=spf1 ip4:52.60.87.177 ip4:54.165.146.13 ip4:54.236.202.218 ip4:35.171.224.16 ip4:34.238.107.229 ip4:54.82.201.179 ip4:18.207.63.80 ip4:34.193.223.166 ip4:34.203.185.172 ip4:34.224.251.10 ip4:18.185.218.157 ip4:34.225.182.221 ip4:18.184.22.138 ip4:52.35.220.252 ip4:52.39.228.22 ip4:52.88.135.56 ip4:54.148.1.33 ip4:54.201.133.252 ip4:35.160.180.46 ip4:44.239.144.125 ip4:44.237.0.252 include:useastemail.verintefm.com -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:xmdevops@verint.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "amazon.com" · 0 issue "amazonaws.com" · 0 issue "amazontrust.com" · 0 issue "comodoca.com" · 0 issue "digicert.com" · 0 issue "letsencrypt.org"
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1313.awsdns-36.org ns-1634.awsdns-12.co.uk ns-400.awsdns-50.com ns-984.awsdns-59.net

✓Registered with eNom, LLC10.2 years old
verintefm.com
✓Registration expiry275 days
2027-06-08
✗Transfer lock
none
✓4 nameservers at registry
ns-1313.awsdns-36.org ns-1634.awsdns-12.co.uk ns-400.awsdns-50.com ns-984.awsdns-59.net

Address	Ports	Edge	Network
3.90.120.171 verintefm.com +2	80443	direct	—
32.197.176.220 verintefm.com +2	80443	direct	—
3.217.138.50 test-efmpreview.verintefm.com +1	80443	direct	—
44.197.65.117 www.sandbox.healthspring.verintefm.com +2	80443	direct	—
44.194.4.234 dbs.verintefm.com +2	80443	direct	—
52.57.230.252 fts.verintefm.com +3	80443	direct	—
98.89.202.100 test-efmpreview.verintefm.com +2	443	direct	—
32.194.57.210 www.sandbox.healthspring.verintefm.com +1	80	direct	—
52.4.252.153 dbs.verintefm.com +2	443	direct	—
10.4.116.169 efm.staging.verintefm.com +1	none known	direct	—
10.4.116.42 efm.staging.verintefm.com +1	none known	direct	—
10.4.116.125 efm.staging.verintefm.com +1	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

verintefm.com security report

Low

Findings

Email authentication

DNS

Registration

Hosts

Hostnames