bayer.us security report

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

86risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

6Medium

17Low

1Info

Collected 7 hours ago25.3sfrom cache

Certificate Transparency147
DNS resolution14
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs21
Registration
DNS posture2
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis27

noteFound 147 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.
noteNo registration data: RDAP has no record at this level.
note1 host was identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 32.193.250.180 (login.cropscience.bayer.us), which advertise jquery ui 1.11.3, internet information services 10.0, bootstrap 3.3.2, asp.net 4.0.30319, jquery 1.10.2. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2020-11023 CVE-2020-11022 CVE-2019-11358 CVE-2019-8331 CVE-2018-20677 CVE-2018-20676 CVE-2018-14042 CVE-2018-14040 CVE-2016-10735 CVE-2015-9251
What to do
Confirm the running versions on 32.193.250.180 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2020-11023 ↗CVE-2020-11022 ↗CVE-2019-11358 ↗CVE-2019-8331 ↗CVE-2018-20677 ↗
asset: 32.193.250.180
Shodan matched these CVEs against the service banners it saw on 13.216.192.42 (login.cropscience.bayer.us), which advertise nginx 1.18.0. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2025-23419 CVE-2023-44487 CVE-2021-23017 CVE-2021-3618
What to do
Confirm the running versions on 13.216.192.42 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗CVE-2021-23017 ↗CVE-2021-3618 ↗
asset: 13.216.192.42
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.bayer.us TXT "v=DMARC1; p=none; rua=mailto:dmarc@bayer.us"`, review the reports, then move to p=quarantine and p=reject.
asset: bayer.us
13.216.192.42 (login.cropscience.bayer.us) reports nginx 1.18.0. 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: 13.216.192.42
32.193.250.180 (login.cropscience.bayer.us) reports jquery ui 1.11.3, internet information services 10.0, bootstrap 3.3.2, asp.net 4.0.30319, jquery 1.10.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: 32.193.250.180
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.bayer.com/en/us/bayer-united-states-of-america
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.bayer.com/en/us/bayer-united-states-of-america
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.bayer.com/en/us/bayer-united-states-of-america
Nothing tells receiving mail servers which hosts may send as @bayer.us, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: bayer.us
stage.maverick.bayer.us 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: stage.maverick.bayer.us
stage.services.bayer.us 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: stage.services.bayer.us
stage.weather.services.bayer.us 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: stage.weather.services.bayer.us
stage.repfinder.services.bayer.us 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: stage.repfinder.services.bayer.us
www.stage.weather.services.bayer.us 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.stage.weather.services.bayer.us
stage.storelocator.services.bayer.us 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: stage.storelocator.services.bayer.us
dev.ace.cm.patientassistance.bayer.us 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.ace.cm.patientassistance.bayer.us
www.stage.repfinder.services.bayer.us 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.stage.repfinder.services.bayer.us
stage.contentfactory.services.bayer.us 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: stage.contentfactory.services.bayer.us
www.stage.storelocator.services.bayer.us 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.stage.storelocator.services.bayer.us
stage.addressvalidation.services.bayer.us 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: stage.addressvalidation.services.bayer.us
origin.stage.contentfactory.services.bayer.us 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: origin.stage.contentfactory.services.bayer.us
www.stage.addressvalidation.services.bayer.us 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.stage.addressvalidation.services.bayer.us
www.origin.stage.contentfactory.services.bayer.us 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.origin.stage.contentfactory.services.bayer.us
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.bayer.com/en/us/bayer-united-states-of-america
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.bayer.com/en/us/bayer-united-states-of-america
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: bayer.us
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: bayer.us

final https://www.bayer.com/en/us/bayer-united-states-of-americastatus 403time 2152msstack cloudflare

–http:// redirects to https://port 80 did not answer
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
pdns1.cscdns.net pdns2.cscdns.net

Address	Ports	CVEs	Edge	Network
75.2.28.136 bayer.us +4	80443	0	direct	—
99.83.202.119 es.bayer.us +3	80443	0	direct	—
13.216.192.42 login.cropscience.bayer.us +1	80443	4	direct	—
52.7.119.224 login.cropscience.bayer.us +1	80443	0	direct	—
32.193.250.180 login.cropscience.bayer.us +2	80443	10	Cloudflare~	—
13.35.36.8 gigya.login.cropscience.bayer.us +3	80443	0	direct	—
13.35.36.86 gigya.login.cropscience.bayer.us +2	80443	0	direct	—
13.35.36.119 gigya.login.cropscience.bayer.us +2	80443	0	direct	—
13.35.36.67 gigya.login.cropscience.bayer.us +11	80443	0	direct	—
34.238.93.234 login.cropscience.bayer.us +1	443	0	direct	—
23.215.7.19 dev.ace.cm.patientassistance.bayer.us +1	80	0	direct	—
23.215.7.15 dev.ace.cm.patientassistance.bayer.us +1	80	0	direct	—

Archived URLs

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

bayer.us security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames