Skip to content

Hostname

escortbabylon.net

Last fetched

escortbabylon.net resolves to 104.20.16.168, announced in 104.20.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. escortbabylon.net 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 · escortbabylon.netRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/escortbabylon.net

Resolution chain

IPv6 resolution

No AAAA record for escortbabylon.net is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1052
Registrant organisation
domains by proxy,
Contact emails
escortbabylon.net.1ib8r15kdneic@domains-anonymizer.com, 907ab1e8c707fda6_o@whoisprivacy.com, escortbabylon.net@domainsbyproxy.com, escortbabylon.net@myprivacy.net

Subdomains

Subdomain
hostmaster.escortbabylon.net
mail.escortbabylon.net
wildcard.escortbabylon.net
www.escortbabylon.net

Showing 4 of 4 subdomains (4 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • amalia.ns.cloudflare.com
  • donovan.ns.cloudflare.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

MX records

  • mail.protonmail.ch

SPF policy

  • include: _spf.protonmail.ch
  • a: escortbabylon.net
  • mx: escortbabylon.net
  • ip: 185.17.144.145

Threat-feed evidence

History

Related pages

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