Skip to content

Hostname

jelastic.team

Last fetched

jelastic.team resolves to 198.244.136.230, announced in 198.244.128.0/17 by OVH - OVH SAS in GB. jelastic.team 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 · jelastic.teamRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/jelastic.team

Resolution chain

IPv6 resolution

No AAAA record for jelastic.team is recorded in WhisperGraph.

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar
iana:291
Registrant organisation
jelastic,
Contact emails
team.operations@jelastic.com

Subdomains

Subdomain
_msa-dev.jelastic.team
_msa.jelastic.team
bhs.jelastic.team
central.jelastic.team
cmp.jelastic.team
gitlab-test.jelastic.team
gitlab-test1.jelastic.team
lab1.jelastic.team
msa-dev.jelastic.team
msa.jelastic.team
one.jelastic.team
tarragona.jelastic.team

Showing 12 of 1,341. View all subdomains →

Mail and authentication

Nameservers

  • waw1-1.jelastic.cloud
  • waw1-2.jelastic.cloud
  • rbx7-1.gate.jelastic.com
  • rbx7-2.gate.jelastic.com
  • waw1-1.gate.jelastic.com
  • waw1-2.gate.jelastic.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

SPF policy

  • include: _msa.jelastic.team
  • include: _msa-dev.jelastic.team

Threat-feed evidence

History

Related pages

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