Check-Host.cc

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

jitsi.github.io

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

DNS Check HTTP Check Run Full Scan .io TLD

Run a live full scan of jitsi.github.io

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
8
A/AAAA targets
Subdomains
10
CT + scan + body
Record Types
3
seen in DNS
Observed Certs
—
in our scans

DNS Records

A
185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153
AAAA
2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153
MX
—
NS
—
TXT
—
CNAME
—
CAA
0 issue "digicert.com", 0 issue "letsencrypt.org", 0 issue "sectigo.com", 0 issuewild "digicert.com", 0 issuewild "letsencrypt.org", 0 issuewild "sectigo.com"

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
jitsi.github.io
185.199.111.153 2606:50c0:8000::153 2606:50c0:8001::153 2606:50c0:8002::153 +4
2026-07-28 19:48:54.308

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.

91.218.112.180:443 href · ×3
130.83.128.193:443 href · ×3
64.227.171.249:443 href · ×3
85.214.96.104:443 href · ×3
45.150.187.200:443 href · ×3
5.78.63.97:443 href · ×3
91.195.56.52:443 href · ×3
20.254.68.27:443 href · ×3
5.188.78.139:443 href · ×3
144.91.67.25:443 href · ×2
37.153.88.204:443 href · ×2
185.26.104.171:443 href · ×2
47.207.63.204:443 href · ×2
213.221.24.145:443 href · ×2
89.167.106.13:443 href · ×2
151.80.147.200:443 href · ×2
45.10.160.119:443 href · ×2
82.177.57.36:443 href · ×2
90.158.121.56:443 href · ×2
193.197.7.46:443 href · ×2
91.134.135.148:443 href · ×2
46.224.128.122:443 href · ×2
185.57.66.97:443 href · ×2
185.226.117.23:443 href · ×2
163.227.224.27:443 href · ×2
145.220.6.30:443 href · ×2
46.10.160.252:443 href · ×2
109.172.115.138:443 href · ×2
117.21.178.54:443 href · ×2
99.91.193.157:443 href · ×2
93.45.240.107:443 href · ×2
2.27.86.253:443 href · ×2
49.12.237.179:443 href · ×2
5.182.21.4:443 href · ×2
82.196.120.74:443 href · ×2
107.170.65.5:443 href · ×2
195.93.253.97:443 href · ×2
185.147.81.11:443 href · ×2
144.126.232.204:443 href · ×2
178.254.35.240:443 href · ×2
87.99.143.145:443 href · ×2
5.75.233.249:443 href · ×2
193.138.81.77:443 href · ×2
212.98.56.147:443 href · ×2
109.123.242.39:443 href · ×2
193.180.213.208:8443 href · ×2
211.126.238.13:443 href · ×2
145.255.5.90:443 href · ×2
137.74.94.120:443 href · ×2
51.83.185.8:443 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

Domain timeline pending

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