Check-Host.cc

Domain

prismjs.com

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

Run a live full scan of prismjs.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
2
A/AAAA targets
Subdomains
13
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
4
in our scans

DNS Records

A
15.197.167.90, 3.33.186.135
AAAA
MX
NS
dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net
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

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain Resolves to Last seen
prismjs.com 2026-07-28 20:23:38.809

Tech Stack

Tech detection pending

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

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

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

89.238.64.65:443 href · ×4
23.17.58.151:80 href · ×4
202.92.215.2:443 href · ×3
162.240.73.28:443 href · ×2
195.182.194.147:443 href · ×2
34.174.232.83:443 href · ×2
108.61.119.160:443 href · ×2
208.109.202.61:80 href · ×2
123.56.226.103:443 href · ×2
143.110.178.82:80 href · ×2
77.81.4.150:80 href · ×2
142.93.22.185:80 href · ×2
182.254.141.213:443 href · ×2
103.60.204.118:80 href · ×2
178.250.156.39:443 href · ×2
35.221.234.220:443 href · ×2
116.203.91.132:80 href · ×2
209.87.229.91:443 href · ×2
34.87.140.96:443 href · ×2
45.141.103.233:80 href · ×2
173.255.246.64:443 href · ×2
47.242.138.253:443 href · ×2
140.238.214.156:443 href · ×2
120.79.72.174:80 href · ×1
103.80.100.149:443 href · ×1
3.89.181.24:443 href · ×1
157.22.205.77:443 href · ×1
109.206.165.2:443 href · ×1
13.52.179.186:80 href · ×1
191.238.215.4:80 href · ×1
195.201.146.223:80 href · ×1
39.107.254.148:443 href · ×1
95.179.133.125:443 href · ×1
198.72.112.15:443 href · ×1
101.53.145.140:443 href · ×1
43.205.31.117:443 href · ×1
62.72.42.205:80 href · ×1
172.238.12.102:443 href · ×1
174.138.127.150:80 href · ×1
107.22.186.231:443 href · ×1
91.62.196.221:443 href · ×1
52.79.107.11:443 href · ×1
198.211.115.131:443 href · ×1
47.116.13.117:443 href · ×1
104.131.54.12:443 href · ×1
5.196.114.215:443 href · ×1
44.194.74.246:443 href · ×1
52.29.155.94:443 href · ×1
3.138.209.198:80 href · ×1
45.56.113.233:80 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
NS dns4.p03.nsone.net 2026-05-25 22:07:29.493 2026-07-28 20:23:38.809
A 15.197.167.90 2026-05-25 22:07:29.493 2026-07-28 20:23:38.809
NS dns1.p03.nsone.net 2026-05-25 22:07:29.493 2026-07-28 20:23:38.809
A 3.33.186.135 2026-05-25 22:07:29.493 2026-07-28 20:23:38.809
NS dns3.p03.nsone.net 2026-05-25 22:07:29.493 2026-07-28 20:23:38.809
NS dns2.p03.nsone.net 2026-05-25 22:07:29.493 2026-07-28 20:23:38.809