Hostname

timo.cz

Last fetched Tue, 15 Sep 2026 04:58:29 GMT

timo.cz resolves to 104.26.4.225, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. timo.cz is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

104.26.4.225
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
104.26.5.225
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
172.67.71.74
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
45.138.107.47
45.138.107.0/24 · WEDOS-GLOBAL - WEDOS Internet, a.s. · Prague, CZ
45.138.107.48
45.138.107.0/24 · WEDOS-GLOBAL - WEDOS Internet, a.s. · Prague, CZ
92.205.23.214
92.205.0.0/19 · GODADDY-SXB - Host Europe GmbH · Frankfurt am Main, DE

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar: registrar:reg-webglobe
Registrant organisation: petr valka dipl.ing.
Contact emails: rma@rma.cz

Subdomains

Subdomain
crm.timo.cz
is.timo.cz
server.timo.cz
www.timo.cz

Showing 4 of 12. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

emerson.ns.cloudflare.com
ines.ns.cloudflare.com
wedos-global-ns-a375snkv.wedos.com
wedos-global-ns-a375snkv.wedos.cz
wedos-global-ns-a375snkv.wedos.eu
wedos-global-ns-a375snkv.wedos.net

MX records

mx.stable.cz

SPF policy

include: sparkpostmail.com
include: spf.smartemailing.cz
include: smtpx.stable.cz
a: timo.cz
mx: timo.cz
include: servers.mcsv.net

Threat-feed evidence

History

Pivot from timo.cz into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "timo.cz"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.