Skip to content
Install MCP

Hostname

physiobeactive.bg

Last fetched

physiobeactive.bg resolves to 185.45.67.130, announced in 185.45.66.0/23 by SUPERHOSTING_AS - SuperHosting.BG Ltd. in BG. physiobeactive.bg 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

WHISPER CANON · physiobeactive.bgRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/physiobeactive.bg

Resolution chain

IPv6 resolution

No AAAA record for physiobeactive.bg is recorded in WhisperGraph.

Attribution

superhosting bg

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for physiobeactive.bg. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
www.physiobeactive.bg

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • dns1.digsys.bg
  • dns2.digsys.bg
  • ns217.superhosting.bg
  • ns218.superhosting.bg
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • physiobeactive.bg

SPF policy

  • a: physiobeactive.bg
  • mx: physiobeactive.bg
  • include: fiesta.spf.superhosting.bg
  • include: smtp-out.spf.superhosting.bg
  • ip: 185.45.66.22
  • ip: 185.45.67.22

Threat-feed evidence

History

Related pages

Pivot from physiobeactive.bg 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: "physiobeactive.bg"})-[: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.