Skip to content

Hostname

masala.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
itp digital
Contact emails
domains@itp.com, 21f47548e88f46ae9c2095c3e1e0b8b6.protect@whoisguard.com, 220b9a1eb6564c409bcf0e7f4146147b.protect@whoisguard.com, 762278b59cc947e1aa46785b0cceecaa.protect@whoisguard.com, da4fc691f41d4240a50af2a3de6e49d0.protect@whoisguard.com, 21b04cc4d287451b8042caab5527e79b.protect@withheldforprivacy.com, c1823c703efb4077a30887d9688d42b7.protect@withheldforprivacy.com

Subdomains

Subdomain
amp.masala.com
dev.masala.com
dev1.masala.com
events.masala.com
www.masala.com

Showing 5 of 5 subdomains (5 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

Mail and authentication

Nameservers

  • ns-388.awsdns-48.com
  • ns-814.awsdns-37.net
  • ns-1135.awsdns-13.org
  • ns-1750.awsdns-26.co.uk

MX records

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com

SPF policy

  • include: amazonses.com
  • include: _spf.createsend.com
  • a: masala.com
  • include: itp.net

Threat-feed evidence

History

Related pages

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