Hostname
global.black
Last fetched
global.black resolves to 184.154.155.98, announced in 184.154.155.0/24 by SINGLEHOP-LLC - Internap Holding LLC in US. global.black is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 184.154.155.98
184.154.155.0/24 · SINGLEHOP-LLC - Internap Holding LLC · Chicago, US
IPv6 resolution
No AAAA record for global.black is recorded in WhisperGraph.
Attribution
internap holding
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- meng xian ping
- Contact emails
- 865623333@qq.com, 998deec09da54e7a860c728663fb3630.protect@withheldforprivacy.com, zinew@qq.com
Subdomains
| Subdomain |
|---|
| cpanel.global.black |
| cpcalendars.global.black |
| cpcontacts.global.black |
| hub.global.black |
| mail.global.black |
| webdisk.global.black |
| webmail.global.black |
| www.global.black |
Showing 8 of 8 subdomains (8 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.
Mail and authentication
Nameservers
- ns1.greengeeks.net
- ns2.greengeeks.net
- 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
- ams-ns1.websitehostserver.net
- chi-ns1.websitehostserver.net
- chi-ns2.websitehostserver.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: 24364337.spf04.hubspotemail.net
- include: spf.websitehostserver.net
- ip: 173.236.65.214
- ip: 184.154.155.98
Threat-feed evidence
History
Related pages
Pivot from global.black 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: "global.black"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.