Check-Host.cc

Try 1.1.1.1 AS13335 check-host.cc /country/de /tld/cc
Domain

jqueryui.com

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

DNS Check HTTP Check Run Full Scan .com TLD

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

DNS Records

A
104.18.228.34, 104.18.229.34
AAAA
2606:4700::6812:e422, 2606:4700::6812:e522
MX
—
NS
george.ns.cloudflare.com, lara.ns.cloudflare.com
TXT
v=spf1 -all
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
bugs.jqueryui.com
143.198.9.136 2a04:4e42:600::411 2a04:4e42::411 2a04:4e42:200::411 +21
2026-07-28 17:13:52.071
api.jqueryui.com
104.18.228.34 2606:4700::6812:e522 2606:4700::6812:e422 104.18.229.34
2026-07-28 02:31:53.233
blog.jqueryui.com
104.18.228.34 104.18.229.34 2606:4700::6812:e522 2606:4700::6812:e422
2026-05-26 20:06:45.970
jqueryui.com
104.18.229.34 2606:4700::6812:e522 2606:4700::6812:e422 104.18.228.34
2026-07-28 19:11:54.346
dev.jqueryui.com
143.198.9.136 104.131.8.164
2026-07-20 03:26:37.146
stage.api.jqueryui.com
45.55.32.91
2026-07-23 23:16:31.277
stage.jqueryui.com
45.55.32.91
2026-07-23 23:16:31.277

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.

135.149.17.74:443 href · ×13
40.81.222.85:443 href · ×13
40.81.222.224:443 href · ×13
40.81.219.44:443 href · ×13
139.15.175.13:80 href · ×12
159.198.43.45:80 href · ×10
67.216.197.161:443 href · ×8
54.37.10.209:443 href · ×8
85.158.1.162:443 href · ×6
128.22.22.84:8888 href · ×6
183.76.81.126:8080 href · ×6
128.22.21.148:8888 href · ×6
220.157.128.53:80 href · ×6
218.219.231.184:80 href · ×6
110.233.131.173:8080 href · ×6
210.156.166.104:80 href · ×6
128.22.26.107:8888 href · ×6
109.93.199.5:80 href · ×5
95.213.231.25:443 href · ×4
84.247.152.222:8443 href · ×4
93.86.61.168:80 href · ×4
5.45.184.67:443 href · ×4
154.26.156.230:8443 href · ×4
87.59.131.7:80 href · ×4
80.251.196.189:8081 href · ×4
212.27.31.56:80 href · ×4
34.160.3.171:443 href · ×4
95.165.132.248:80 href · ×4
65.20.110.212:80 href · ×4
31.13.213.32:443 href · ×4
91.150.107.78:80 href · ×4
202.238.215.43:8080 href · ×3
219.121.53.248:80 href · ×3
128.22.22.20:8888 href · ×3
119.240.240.223:8888 href · ×3
128.22.26.251:8888 href · ×3
128.22.22.17:8888 href · ×3
128.22.26.254:8888 href · ×3
150.66.105.10:8888 href · ×3
157.107.204.128:8080 href · ×3
107.153.48.20:8888 href · ×3
128.22.21.167:8888 href · ×3
133.159.133.108:8080 href · ×3
153.141.162.148:8080 href · ×3
34.234.53.56:443 href · ×3
119.240.106.7:80 href · ×3
121.87.152.9:8888 href · ×3
153.152.78.125:8888 href · ×3
121.87.156.5:8888 href · ×3
183.76.86.103:80 href · ×3

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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.