Skip to content

Hostname

milano.com.br

Last fetched

milano.com.br resolves to 159.65.229.76, announced in 159.65.224.0/20 by DIGITALOCEAN-ASN - DigitalOcean, LLC in US. milano.com.br 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 · milano.com.brRouting diversity2.4/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/milano.com.br

Resolution chain

IPv6 resolution

No AAAA record for milano.com.br is recorded in WhisperGraph.

Attribution

digitalocean

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrant organisation
loja de calcados milano.com.br ltda
Contact emails
ney@milano.com.br

Subdomains

Subdomain
allin.milano.com.br
b2b.milano.com.br
campanha.milano.com.br
cpanel.milano.com.br
cpcalendars.milano.com.br
cpcontacts.milano.com.br
dna.milano.com.br
imgsw.milano.com.br
lp.milano.com.br
mail.milano.com.br
meuspedidos.milano.com.br
modafeminina.milano.com.br

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

  • ns1.aldeiadigital.com.br
  • server1.aldeiadigital.com.br
  • server2.aldeiadigital.com.br
  • ns2.aldeiadigital.com.br

MX records

  • milano.com.br

SPF policy

  • ip: 198.11.247.88/29
  • include: aldeiadigital.com.br
  • include: spf1.auinmeio.com.br
  • include: spf2.auinmeio.com.br
  • a: milano.com.br
  • mx: milano.com.br
  • include: spf.mandrillapp.com
  • include: relay.mailbaby.net
  • ip: 104.238.131.14
  • ip: 107.170.25.51
  • ip: 159.65.229.76
  • ip: 198.11.241.82
  • ip: 198.11.247.92

Threat-feed evidence

History

Related pages

Pivot from milano.com.br 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: "milano.com.br"})-[: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.