Skip to content

Hostname

norbits.net

Last fetched

norbits.net resolves to 185.141.63.212, announced in 185.141.63.0/24 by belcloud - Belcloud LTD in BG. norbits.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 · norbits.netRouting diversity1.5/10Peering density8.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/norbits.net

Resolution chain

IPv6 resolution

No AAAA record for norbits.net is recorded in WhisperGraph.

Attribution

belcloud

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Contact emails
04ce0d0537204b5e919db19c9503c1cb.protect@whoisguard.com, 35e75efea95f4f478319828afcce3033.protect@whoisguard.com, e1277bd9848e40f8ba79d824c2412922.protect@whoisguard.com, ae3070fe46704717bbf67acad6661b70.protect@withheldforprivacy.com, e245b133a5974802884f5f8bb4ae32d1.protect@withheldforprivacy.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
  • 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

  • mail.protonmail.ch
  • mailsec.protonmail.ch

SPF policy

  • include: _spf.protonmail.ch

Threat-feed evidence

History

Related pages

Pivot from norbits.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: "norbits.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.