biocatch.com security report

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

34risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

0Medium

21Low

2Info

Collected 9 hours ago4.8sfrom cache

Certificate Transparency191
DNS resolution22
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs33
Registration
DNS posture2
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis24

noteFound 191 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://www.biocatch.com/
grafana-devops.customers.biocatch.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: grafana-devops.customers.biocatch.com
login-test.customers.biocatch.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: login-test.customers.biocatch.com
api.dev.bc2.customers.biocatch.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: api.dev.bc2.customers.biocatch.com
wup.dev.bc2.customers.biocatch.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: wup.dev.bc2.customers.biocatch.com
demo.dev.bc2.customers.biocatch.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: demo.dev.bc2.customers.biocatch.com
login-qa.bc2.customers.biocatch.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: login-qa.bc2.customers.biocatch.com
logs.dev.bc2.customers.biocatch.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: logs.dev.bc2.customers.biocatch.com
login-dev.bc2.customers.biocatch.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: login-dev.bc2.customers.biocatch.com
bc-test-client.customers.biocatch.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: bc-test-client.customers.biocatch.com
avivapi.dev.bc2.customers.biocatch.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: avivapi.dev.bc2.customers.biocatch.com
avivwup.dev.bc2.customers.biocatch.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: avivwup.dev.bc2.customers.biocatch.com
mosh-test-login.customers.biocatch.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: mosh-test-login.customers.biocatch.com
api-pull.dev.bc2.customers.biocatch.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: api-pull.dev.bc2.customers.biocatch.com
avivdemo.dev.bc2.customers.biocatch.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: avivdemo.dev.bc2.customers.biocatch.com
avivlogs.dev.bc2.customers.biocatch.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: avivlogs.dev.bc2.customers.biocatch.com
aziziapi.dev.bc2.customers.biocatch.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: aziziapi.dev.bc2.customers.biocatch.com
aziziwup.dev.bc2.customers.biocatch.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: aziziwup.dev.bc2.customers.biocatch.com
katiaapi.dev.bc2.customers.biocatch.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: katiaapi.dev.bc2.customers.biocatch.com
katiawup.dev.bc2.customers.biocatch.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: katiawup.dev.bc2.customers.biocatch.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: biocatch.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: biocatch.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: biocatch.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: biocatch.com

final https://www.biocatch.com/status 200time 1455msstack cloudflare · HubSpot

✗http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000
✓Content-Security-Policy
upgrade-insecure-requests
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
no-referrer-when-downgrade
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none
✓Cookie _cfuvid
Secure · HttpOnly · SameSite=none

✓Receives mail via 1 server
biocatch-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 ip4:34.141.90.172 ip4:34.107.47.119 include:_spf.google.com include:1828513.spf07.hubspotemail.net include:u8059028.wl029.sendgrid.net include:spf.protection.outlook.com include:_spf.salesforce.com include:spf-de.emailsignatures365.com include:em9009.seismic.com -all
✓DMARCp=reject
v=DMARC1; p=reject; sp=reject; pct=100; ri=86400; rua=mailto:postmaster@biocatch.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
pdns03.domaincontrol.com pdns04.domaincontrol.com

✓Registered with GoDaddy.com, LLC15.9 years old
biocatch.com
!Registration expiry37 days
2026-10-14
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
pdns03.domaincontrol.com pdns04.domaincontrol.com

Address	Ports	Edge	Network
199.60.103.31 www.biocatch.com +3	80443205220532082208320862087+5	Cloudflare~	—
199.60.103.225 www.biocatch.com +5	80443205220532082208320862087+5	Cloudflare~	—
15.197.225.128 biocatch.com +3	80443	direct	—
3.33.251.168 biocatch.com +3	80443	direct	—
150.171.110.102 login-test.customers.biocatch.com +4	80443	direct	—
51.124.18.36 wup.dev.bc2.customers.biocatch.com +14	443	direct	—
20.229.21.157 grafana-devops.customers.biocatch.com	none known	direct	—

Archived URLs

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

biocatch.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames