Skip to content

Hostname

nobelglobe.com

Last fetched

nobelglobe.com resolves to 208.64.6.190, announced in 208.64.6.0/23 by NL-820-21958 - Nobel Ltd in BM. nobelglobe.com 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 · nobelglobe.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/nobelglobe.com

Resolution chain

IPv6 resolution

No AAAA record for nobelglobe.com is recorded in WhisperGraph.

Attribution

nobel

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
nobel, ltd. thomas knobel
Contact emails
domains@nobelglobe.com, f36e2afeba8b4fceb714bea236e1a0d5.protect@whoisguard.com, 073862dcd2ef4c8aa2bf5c4e43fa3637.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.nobelglobe.com
  • dns2.nobelglobe.com
  • dns3.nobelglobe.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

  • mailgw01.nobelglobe.com
  • mailgw02.nobelglobe.com

SPF policy

  • include: _spf.nobelglobe.com
  • include: spf.protection.outlook.com
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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