Check-Host.cc

Domain

www.elsevier.com

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of www.elsevier.com

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
A/AAAA targets
Subdomains
CT + scan + body
Record Types
seen in DNS
Observed Certs
in our scans

DNS Records

A
104.17.38.96, 104.17.39.96
AAAA
MX
NS
TXT
CNAME
CAA

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Subject: *.elsevier.com
Issuer: GlobalSign RSA OV SSL CA 2018
SANs: *.elsevier.com, elsevier.com, www.elsevier.com
Subject: *.elsevier.com
Issuer: GlobalSign RSA OV SSL CA 2018
SANs: *.elsevier.com, elsevier.com, www.elsevier.com
Subject: *.elsevier.com
Issuer: GlobalSign RSA OV SSL CA 2018
SANs: *.elsevier.com, elsevier.com, www.elsevier.com
Subject: *.elsevier.com
Issuer: GlobalSign RSA OV SSL CA 2018
SANs: *.elsevier.com, elsevier.com, www.elsevier.com

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

34.200.153.181:443 href · ×10
18.215.25.134:443 href · ×7
32.196.169.253:443 href · ×7
35.173.67.86:443 href · ×6
161.82.216.173:80 href · ×6
161.82.216.173:443 href · ×6
107.21.116.116:443 href · ×6
32.198.128.122:443 href · ×6
54.74.213.108:443 href · ×5
3.209.5.127:443 href · ×4
100.30.56.62:443 href · ×4
100.27.52.220:443 href · ×4
128.118.162.112:443 href · ×3
212.122.198.131:80 href · ×3
121.192.177.222:80 href · ×2
91.134.138.83:80 href · ×2
210.86.226.167:8080 href · ×2
84.237.18.154:80 href · ×2
202.28.77.130:443 href · ×2
137.43.44.24:80 href · ×2
85.143.113.32:80 href · ×2
41.138.161.87:443 href · ×1
122.114.236.173:443 href · ×1
132.204.176.13:80 href · ×1
147.139.167.165:80 href · ×1
172.236.155.92:443 href · ×1
43.153.107.96:8080 href · ×1
54.250.144.171:443 href · ×1
95.129.137.186:443 href · ×1
147.139.167.165:443 href · ×1
140.118.5.28:443 href · ×1
95.129.137.186:80 href · ×1
89.108.72.213:443 href · ×1
137.43.44.24:443 href · ×1
131.246.112.7:80 href · ×1
217.147.232.89:443 href · ×1
193.233.3.162:443 href · ×1
45.113.233.40:80 href · ×1
202.28.77.130:80 href · ×1
103.102.149.59:8443 href · ×1
31.202.13.162:443 href · ×1
89.104.84.241:443 href · ×1
159.203.216.192:80 href · ×1
5.150.254.75:80 href · ×1
41.59.86.232:443 href · ×1
103.130.82.231:443 href · ×1
104.131.45.179:443 href · ×1
103.67.188.205:8000 href · ×1

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
A 104.17.39.96 2026-05-25 21:56:50.553 2026-07-31 12:13:50.878
A 104.17.38.96 2026-05-25 21:56:50.553 2026-07-31 12:13:50.878