Skip to content

Hostname

globus-ltd.com

Last fetched

globus-ltd.com resolves to 77.223.109.90, announced in 77.223.108.0/22 by SELECTEL-MSK - JSC Selectel in RU. globus-ltd.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 · globus-ltd.comRouting diversity1.5/10Peering density6.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/globus-ltd.com

Resolution chain

IPv6 resolution

No AAAA record for globus-ltd.com is recorded in WhisperGraph.

Attribution

jsc selectel

ORIGIN_AS

WHOIS identity

Registrar
iana:1606
Registrant organisation
'globus-it',
Contact emails
it@globus-ltd.com, services@globus-ltd.com, info@domain-contact.org

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

  • 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
  • ns1.selectel.org
  • ns2.selectel.org
  • ns3.selectel.org
  • ns4.selectel.org
  • ns1.selectel.ru
  • ns2.selectel.ru
  • ns3.selectel.ru
  • ns4.selectel.ru

MX records

  • mx.yandex.net

SPF policy

  • include: mxsspf.sendpulse.com
  • include: spf.unisender.com
  • include: _spf.yandex.net
  • include: spf.sendsay.ru
  • ip: 77.223.109.82
  • ip: 77.223.109.83
  • ip: 77.223.109.84
  • ip: 77.223.109.85
  • ip: 77.223.109.86
  • ip: 77.223.109.87
  • ip: 77.223.109.89
  • ip: 82.208.80.248

Threat-feed evidence

History

Related pages

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