Check-Host.cc

Domain

kb.plesk.com

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

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

DNS Records

A
104.18.40.121, 172.64.147.135
AAAA
2606:4700:440b::ac40:9387, 2a06:98c1:3104::6812:2879, 2a06:98c1:3105::ac40:9387, 2a06:98c1:3107::6812:2879
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

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.

46.105.32.150:8443 href · ×4
37.97.235.136:8443 href · ×4
218.40.196.249:80 href · ×4
138.68.6.21:8443 href · ×4
77.68.12.155:8443 href · ×4
37.61.200.238:8443 href · ×4
150.107.72.63:8443 href · ×4
85.214.246.220:8443 href · ×4
82.223.39.196:8443 href · ×4
82.223.20.157:8443 href · ×4
8.224.33.44:8443 href · ×4
51.38.239.183:8443 href · ×4
134.209.26.212:8443 href · ×4
54.36.81.118:80 href · ×3
137.74.102.35:443 href · ×3
192.99.76.43:443 href · ×3
210.152.148.186:80 href · ×3
188.165.58.249:443 href · ×3
40.69.24.104:443 href · ×3
218.40.198.140:80 href · ×3
91.142.213.139:80 href · ×3
218.40.197.252:80 href · ×3
31.193.2.26:443 href · ×3
83.169.7.248:80 href · ×3
218.40.192.14:443 href · ×3
218.40.196.240:80 href · ×3
151.80.11.175:80 href · ×3
218.40.196.123:80 href · ×3
86.109.170.67:443 href · ×3
191.252.96.216:80 href · ×3
51.254.242.196:80 href · ×3
109.238.2.124:80 href · ×3
191.252.96.127:443 href · ×3
149.202.170.102:443 href · ×3
222.165.190.237:80 href · ×3
218.40.198.36:80 href · ×3
217.113.1.154:80 href · ×3
109.238.2.124:443 href · ×3
138.201.202.206:80 href · ×3
219.99.166.83:443 href · ×3
213.142.137.179:80 href · ×3
74.208.157.244:443 href · ×3
188.164.198.58:443 href · ×3
124.150.134.233:443 href · ×3
218.40.193.113:443 href · ×3
81.169.247.11:80 href · ×3
217.61.13.30:80 href · ×2
213.229.106.194:80 href · ×2
191.252.95.179:443 href · ×2
218.40.199.169:80 href · ×2

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
AAAA 2606:4700:440b::ac40:9387 2026-05-25 21:56:50.553 2026-06-24 00:50:23.386
A 104.18.40.121 2026-05-25 21:56:50.553 2026-07-28 20:47:52.650
A 172.64.147.135 2026-05-25 21:56:50.553 2026-07-28 20:47:52.650
AAAA 2a06:98c1:3104::6812:2879 2026-05-25 21:56:50.553 2026-06-24 00:50:23.386
AAAA 2a06:98c1:3107::6812:2879 2026-07-15 20:54:20.174 2026-07-28 20:47:52.650
AAAA 2a06:98c1:3105::ac40:9387 2026-07-15 20:54:20.174 2026-07-28 20:47:52.650