Skip to content

Hostname

theleela.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1495
Registrant organisation
amandeep sarna
Contact emails
vishwas.joshi@theleela.com, srinivasan.m@theleela.com, amandeep.sarna@theleela.com, lajja.sureka@theleela.com, webmaster@theleela.com

Subdomains

Subdomain
edm.theleela.com
elink.theleela.com
giftcard.theleela.com
images.theleela.com
itcare.theleela.com
kov.theleela.com
magazine.theleela.com
reservations.theleela.com
shop.theleela.com
staging.theleela.com
test.theleela.com
uat.theleela.com

Showing 12 of 15. 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-58.awsdns-07.com
  • ns-1001.awsdns-61.net
  • ns-1341.awsdns-39.org
  • ns-1847.awsdns-38.co.uk

MX records

  • theleela-com.mail.protection.outlook.com

SPF policy

  • include: ncfp.asia
  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: spf.salesforce.com
  • include: ausmail.synxis.com
  • include: ltxmail.synxis.com
  • include: spf.synxis.com
  • a: theleela.com

Threat-feed evidence

History

Related pages

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