Skip to content

Hostname

timestore.bg

Last fetched

timestore.bg resolves to 2 IPv4 addresses operated by AS43541 in CZ.

Nutrition Label

WHISPER CANON · timestore.bgRouting diversity2.4/10Peering density5.2/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/timestore.bg

Resolution chain

timestore.bg resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

WHOIS identity

No WHOIS records are currently associated with timestore.bg in WhisperGraph.

Subdomains

15 observed subdomains of timestore.bg.

Web-graph footprint

Distinct hostnames that link to or from timestore.bg in the public web crawl.

Threat posture

History

Mail and authentication

SPF policy

12 SPF mechanisms authorising senders for timestore.bg.

MechanismTarget
SPF_Atimestore.bg
SPF_INCLUDE_spf.websupport.sk
SPF_IP185.59.211.161
SPF_IP185.59.211.162
SPF_IP185.59.211.163
SPF_IP185.59.211.181
SPF_IP185.59.211.182
SPF_IP185.59.211.183
SPF_IP185.59.211.184
SPF_IP185.59.211.185
SPF_IP213.109.167.0/24
SPF_MXtimestore.bg

Related pages

Pivot deeper into the graph from timestore.bg.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

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

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