Skip to content

Hostname

isabi.space

Last fetched

isabi.space resolves to 104.21.28.9, announced in 104.22.43.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. isabi.space 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 · isabi.spaceRouting diversity3.9/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.4/10canon.whisper.security/host/isabi.space

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1509

Subdomains

Subdomain
app.isabi.space
autodiscover.isabi.space
cloud.isabi.space
cpanel.isabi.space
cpcalendars.isabi.space
cpcontacts.isabi.space
mail.isabi.space
trade.isabi.space
webdisk.isabi.space
webmail.isabi.space
www.isabi.space

Showing 11 of 13. View all subdomains →

Mail and authentication

Nameservers

  • ns-92.awsdns-11.com
  • aaron.ns.cloudflare.com
  • piper.ns.cloudflare.com
  • ns53.nvme-servers.com
  • ns54.nvme-servers.com
  • ns56.nvme-servers.com
  • ns57.nvme-servers.com
  • vivid1.gfireservers.in
  • vivid2.gfireservers.in
  • ns-532.awsdns-02.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
  • ns-1149.awsdns-15.org
  • ns-1726.awsdns-23.co.uk

MX records

  • isabi.space
  • mail.isabi.space

SPF policy

  • ip: 152.53.210.62/32
  • include: spf-c.mailbaby.net
  • a: isabi.space
  • mx: isabi.space
  • ip: 152.53.54.168

Threat-feed evidence

History

Related pages

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