Skip to content

Hostname

novibets.org

Last fetched

novibets.org resolves to 162.254.39.121, announced in 162.254.39.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. novibets.org 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 · novibets.orgRouting diversity2.4/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint9.2/10canon.whisper.security/host/novibets.org

Resolution chain

IPv6 resolution

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf

Subdomains

Subdomain
mail.novibets.org
webmail.novibets.org
www.novibets.org

Showing 3 of 3 subdomains (3 per page).

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

  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.com
  • a0.org.afilias-nst.info
  • a2.org.afilias-nst.info
  • c0.org.afilias-nst.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
  • b0.org.afilias-nst.org
  • b2.org.afilias-nst.org
  • d0.org.afilias-nst.org
  • ns2.lander.d.parity.domains
  • ns1.lander.d.parity.domains

MX records

  • mx1-hosting.jellyfish.systems
  • mx2-hosting.jellyfish.systems
  • mx3-hosting.jellyfish.systems

SPF policy

  • include: spf.web-hosting.com
  • a: novibets.org
  • mx: novibets.org
  • ip: 162.254.39.51

Threat-feed evidence

History

Related pages

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