Skip to content

Hostname

monitoring.bg

Last fetched

monitoring.bg resolves to 1 IPv4 address operated by A1 in BG.

Nutrition Label

WHISPER CANON · monitoring.bgRouting diversity1.5/10Peering density9.1/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/monitoring.bg

Resolution chain

monitoring.bg resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
213.169.35.3213.169.32.0/19AS8717A1BG

WHOIS identity

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

Subdomains

14 observed subdomains of monitoring.bg.

Web-graph footprint

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

1,309 sites link to this hostname.

Threat posture

History

Mail and authentication

SPF policy

8 SPF mechanisms authorising senders for monitoring.bg.

MechanismTarget
SPF_Amonitoring.bg
SPF_INCLUDEdroid.spf.superhosting.bg
SPF_INCLUDEsmtp-out.spf.superhosting.bg
SPF_IP195.191.148.12
SPF_IP195.191.148.251
SPF_IP195.191.149.12
SPF_IP77.78.150.4
SPF_MXmonitoring.bg

Related pages

Pivot deeper into the graph from monitoring.bg.

Cypher and MCP

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

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