Skip to content

Hostname

esimsar.com

Last fetched

esimsar.com resolves to 3.175.207.103, announced in 3.175.207.0/24 by AMAZON-02 - Amazon.com, Inc. in HK. esimsar.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 · esimsar.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/esimsar.com

Resolution chain

IPv6 resolution

No AAAA record for esimsar.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1011
Registrant organisation
digital privacy corporation
Contact emails
199287.ralhkggu8ql@digitalprivacy.co, admin@esimsar.com

Subdomains

Subdomain
cjwtfp.esimsar.com
images.esimsar.com
m.esimsar.com
marketing.esimsar.com
on.esimsar.com
register.esimsar.com
staging.esimsar.com
www.esimsar.com

Showing 8 of 9. View all subdomains →

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

Mail and authentication

Nameservers

  • ns-229.awsdns-28.com
  • ns-890.awsdns-47.net
  • ns-1121.awsdns-12.org
  • ns-1952.awsdns-52.co.uk

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: amazonses.com
  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: mail.zendesk.com
  • include: support.zendesk.com
  • include: servers.mcsv.net
  • ip: 208.95.134.81

Threat-feed evidence

History

Related pages

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