Skip to content

Hostname

thunder.bg

Last fetched

thunder.bg resolves to 2 IPv4 addresses operated by A1 in BG.

Nutrition Label

WHISPER CANON · thunder.bgRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/thunder.bg

Resolution chain

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

IPPrefixASNOperatorCountry
87.227.135.18787.227.128.0/17AS8717A1BG
95.87.254.12395.87.192.0/18AS8866VIVACOM-AS BULGARIABG

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

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

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

3 SPF mechanisms authorising senders for thunder.bg.

MechanismTarget
SPF_IP195.230.5.128/28
SPF_IP87.227.135.184/29
SPF_IP95.87.254.120/29

Related pages

Pivot deeper into the graph from thunder.bg.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "thunder.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.