Skip to content

Hostname

bvk.rs

Last fetched

bvk.rs resolves to 212.200.255.220, announced in 212.200.240.0/20 by TELEKOM-AS - TELEKOM SRBIJA a.d. in RS. bvk.rs 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 · bvk.rsRouting diversity1.5/10Peering density8.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/bvk.rs

Resolution chain

IPv6 resolution

No AAAA record for bvk.rs is recorded in WhisperGraph.

Attribution

telekom srbija

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bvk.rs. 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
aurora.bvk.rs
autodiscover.bvk.rs
bvkrouter.bvk.rs
cpu2.bvk.rs
danvod.bvk.rs
exwebvk.bvk.rs
mail.bvk.rs
nabavke.bvk.rs
ns.bvk.rs
pegazus.bvk.rs
pionir.bvk.rs
relay.bvk.rs

Showing 12 of 18. 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns.bvk.rs
  • relay.bvk.rs
  • dagda1.isp.telekom.rs

MX records

  • relay.bvk.rs
  • relay3.bvk.rs
  • relay4.bvk.rs

SPF policy

  • ip: 212.200.75.14/32
  • ip: 212.200.75.2/32
  • ip: 212.200.75.48/32
  • a: bvk.rs
  • mx: bvk.rs
  • a: relay.bvk.rs
  • a: relay3.bvk.rs
  • a: relay4.bvk.rs

Threat-feed evidence

History

Related pages

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