Skip to content

Hostname

globemoon.net

Last fetched

globemoon.net resolves to 204.44.192.66, announced in 204.44.192.0/20 by HOSTP-LA - HostPapa in US. globemoon.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 · globemoon.netRouting diversity2.4/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/globemoon.net

Resolution chain

IPv6 resolution

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

Attribution

hostpapa

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
06064ba0fd1f4d8b8ac7af6e7a15a2a0.protect@whoisguard.com, 51184d6624c64857a1ffe07163c72480.protect@whoisguard.com, 252802ada8384d258cd75f151e0ca9c5.protect@withheldforprivacy.com

Subdomains

Subdomain
abc123.globemoon.net
brhnetwork.globemoon.net
cpanel.globemoon.net
cpcalendars.globemoon.net
cpcontacts.globemoon.net
emrosefoods.globemoon.net
mail.globemoon.net
phpeacock.globemoon.net
webdisk.globemoon.net
webmail.globemoon.net
www.globemoon.net

Showing 11 of 14. 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.lp.hostpapa.com
  • ns2.lp.hostpapa.com
  • ns1.hostpapa.com
  • ns2.hostpapa.com
  • ns1.lunarbreeze.com
  • ns2.lunarbreeze.com

MX records

  • globemoon.net

SPF policy

  • include: spf.antispamcloud.com
  • a: globemoon.net
  • mx: globemoon.net
  • include: spf.servername.online
  • ip: 204.44.192.66
  • ip: 216.222.199.203
  • ip: 64.50.187.217

Threat-feed evidence

History

Related pages

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