Skip to content

Hostname

x-elio.com

Last fetched

x-elio.com resolves to 20.55.103.191, announced in 20.48.0.0/12 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. x-elio.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 · x-elio.comRouting diversity1.5/10Peering density7.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/x-elio.com

Resolution chain

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

Registrar
iana:379
Registrant organisation
aurora energy holding
Contact emails
sergio.gonzalez@gestampren.com, netandsec@einzelnet.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

  • dns27.servidoresdns.net
  • dns28.servidoresdns.net

MX records

  • xelio-com0c.mail.protection.outlook.com

SPF policy

  • ip: 149.72.156.108/32
  • ip: 162.218.1.150/32
  • ip: 162.218.1.205/32
  • ip: 162.218.1.206/32
  • ip: 167.89.75.22/32
  • ip: 168.245.112.229/32
  • ip: 162.218.0.230/32
  • ip: 159.135.238.30/32
  • ip: 168.245.64.30/32
  • ip: 209.85.220.41/32
  • ip: 54.240.57.46/32
  • ip: 54.240.57.47/32
  • include: _spf.psm.knowbe4.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: email.signaturit.com
  • mx: x-elio.com
  • ip: 130.214.164.67
  • ip: 153.142.3.227
  • ip: 153.156.20.247
  • ip: 153.156.6.61
  • ip: 159.183.130.64
  • ip: 186.10.15.178
  • ip: 190.109.192.180
  • ip: 190.96.22.82
  • ip: 194.164.160.148
  • ip: 200.188.6.118
  • ip: 213.0.110.242
  • ip: 3.120.181.200
  • ip: 50.210.130.213
  • ip: 85.18.31.10
  • ip: 93.51.240.130

Threat-feed evidence

History

Related pages

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