Skip to content

Hostname

bugy.sk

Last fetched

bugy.sk resolves to 185.59.208.190, announced in 185.59.208.0/22 by VSHOSTING - VSHOSTING-CDN in CZ. bugy.sk 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 · bugy.skRouting diversity1.5/10Peering density5.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/bugy.sk

Resolution chain

IPv6 resolution

No AAAA record for bugy.sk is recorded in WhisperGraph.

Attribution

vshosting

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bugy.sk. 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
targito.bugy.sk
www.bugy.sk

Showing 2 of 4. 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

Mail and authentication

Nameservers

  • ns1.regzone.cz
  • ns1.regzone.de
  • ns1.regzone.info
  • 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

  • 10mx.zoner.com
  • 15mx.zoner.com
  • relay.zoner.com

SPF policy

  • include: _spf.myshoptet.com
  • include: spf-zoner-zmail.zoner.com
  • include: _spf.jupiter.salesmanago.pl
  • a: bugy.sk
  • mx: bugy.sk
  • ip: 185.59.208.190

Threat-feed evidence

History

Related pages

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