Check-Host.cc

Domain

tim.bz

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

Run a live full scan of tim.bz

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

DNS Records

A
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

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
acp-apply-api.internal.tim.bz
1970-01-01 00:00:00.000
acp-apply-api.ts.tim.bz
1970-01-01 00:00:00.000
acp-ops.internal.tim.bz
1970-01-01 00:00:00.000
acp-ops.ts.tim.bz
1970-01-01 00:00:00.000
actual.internal.tim.bz
1970-01-01 00:00:00.000
actual.ts.tim.bz
1970-01-01 00:00:00.000
apply.acp.clients.tim.bz 2026-06-15 14:24:53.999
apply.acp.internal.tim.bz 2026-06-15 14:24:53.999
apply.acp.ts.tim.bz 2026-06-15 14:24:53.999
audiobooks.internal.tim.bz
1970-01-01 00:00:00.000
audiobooks.ts.tim.bz
1970-01-01 00:00:00.000
bizlock.ifi.internal.tim.bz
1970-01-01 00:00:00.000
bizlock.ifi.ts.tim.bz
1970-01-01 00:00:00.000
browser.internal.clients.tim.bz
1970-01-01 00:00:00.000
browser.internal.internal.tim.bz
1970-01-01 00:00:00.000
browser.internal.ts.tim.bz
1970-01-01 00:00:00.000
example.internal.tim.bz
1970-01-01 00:00:00.000
give.acp.clients.tim.bz 2026-07-26 04:14:37.123
give.acp.internal.tim.bz 2026-07-26 04:14:37.123
give.acp.ts.tim.bz 2026-07-26 04:14:37.123
grafana.internal.tim.bz
1970-01-01 00:00:00.000
grafana.ts.tim.bz
1970-01-01 00:00:00.000
hass.internal.tim.bz 2026-06-22 22:39:43.512
hass.ts.tim.bz 2026-06-22 22:39:43.512
irc.internal.tim.bz 2026-07-16 06:44:54.801
irc.ts.tim.bz 2026-07-16 06:44:54.801
lab.clients.tim.bz 2026-06-17 21:52:31.453
lab.internal.tim.bz 2026-06-17 21:52:31.453
lab.ts.tim.bz 2026-06-17 21:52:31.453
mailpit.internal.tim.bz 2026-06-18 05:24:20.870
mailpit.ts.tim.bz 2026-06-18 05:24:20.870
privsy.ifi.internal.tim.bz
1970-01-01 00:00:00.000
privsy.ifi.ts.tim.bz
1970-01-01 00:00:00.000
surveys.acp.clients.tim.bz 2026-07-27 20:51:25.313
surveys.acp.internal.tim.bz 2026-07-27 20:51:25.313
surveys.acp.ts.tim.bz 2026-07-27 20:51:25.313
traefik.internal.tim.bz 2026-07-23 01:41:29.025
traefik.ts.tim.bz
1970-01-01 00:00:00.000
vault.internal.tim.bz
1970-01-01 00:00:00.000
vault.ts.tim.bz
1970-01-01 00:00:00.000
watson.tim.bz 2026-06-03 21:41:11.104
whoami.internal.tim.bz 2026-07-25 11:11:23.829
whoami.ts.tim.bz
1970-01-01 00:00:00.000
www.acp.clients.tim.bz 2026-06-20 04:04:11.946
www.acp.internal.tim.bz 2026-06-20 04:04:11.946
www.acp.ts.tim.bz 2026-06-20 04:04:11.946
yt.internal.tim.bz
1970-01-01 00:00:00.000
yt.ts.tim.bz
1970-01-01 00:00:00.000

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

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

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.