Skip to content

Hostname

asiansouls.com

Last fetched

asiansouls.com resolves to 104.18.18.18, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. asiansouls.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 · asiansouls.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/asiansouls.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1387
Registrant organisation
c/o whoisproxy.com
Contact emails
domains@renewal-service.com, whois@whois-gateway.com, ff42c5b5d0@asiansouls.com.whoistrustee.com, system-noticescom@obscure.me, pw-0741695b8faf7aabe7ab5a9aa32d86f0@privacyguardian.org, pw-9aaecd3e000c24a934ad2e4b51689285@privacyguardian.org, 643207c98856856708a6bbbb6f549242767f63aa363648cb467d0c07c66a597d@asiansouls.com.whoisproxy.org, 8a9fb9c20af071ab5550b1b26aee3ae964e21c9ac371f2836efb326b812c0285@asiansouls.com.whoisproxy.org, aefff0b51d32bd4eb08d63379a7dcb33070100e91804f99a01d98db8cc7fdc38@asiansouls.com.whoisproxy.org, cd5c20428f871626b17388a4d35a2fca894630999b45324550febb555d4162ca@asiansouls.com.whoisproxy.org

Subdomains

Subdomain
n.asiansouls.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • josh.ns.cloudflare.com
  • rayne.ns.cloudflare.com

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: _spf.google.com
  • include: mail.zendesk.com
  • include: spf.sendios.io

Threat-feed evidence

History

Related pages

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