Skip to content

Hostname

weburg.net

Last fetched

weburg.net resolves to 212.49.103.220, announced in 212.49.96.0/19 by MIRALOGIC-AS - LLC "KomTehCentr" in RU. weburg.net 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 · weburg.netRouting diversity1.5/10Peering density5.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/weburg.net

Resolution chain

IPv6 resolution

Attribution

komtehcentr

ORIGIN_AS

WHOIS identity

Registrar
iana:1011
Registrant organisation
weburg ltd. shlema cutzelsson ext
Contact emails
21422b.rir3xflh89s@digitalprivacy.co, shlema.cutzelsson@gmail.com

Subdomains

Subdomain
app0.weburg.net
app1.weburg.net
best2012.weburg.net
bt.weburg.net
cp.weburg.net
db.weburg.net
gl.weburg.net
gl00.weburg.net
hotspot.weburg.net
img.weburg.net
m.weburg.net
ns0.weburg.net

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

  • 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
  • ns0.weburg.net
  • ns1.weburg.net

MX records

  • relay2.miralogic.ru
  • relay3.miralogic.ru

SPF policy

  • a: mail.mirasystem.net
  • mx: weburg.net
  • a: relay0.mail.miralogic.ru
  • a: relay1.mail.miralogic.ru
  • ip: 212.49.119.90
  • ip: 212.49.119.93
  • ip: 2a02:17d0:8006:2:0:0:0:2
  • ip: 2a02:17d0:8006:2:0:0:0:3

Threat-feed evidence

History

Related pages

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