Skip to content

Hostname

2morrowsports.com.br

Last fetched

2morrowsports.com.br resolves to 52.84.127.112, announced in 52.84.120.0/21 by AMAZON-02 - Amazon.com, Inc. in US. 2morrowsports.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 · 2morrowsports.com.brRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/2morrowsports.com.br

Resolution chain

IPv6 resolution

No AAAA record for 2morrowsports.com.br is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
am de freitas solu??es - me
Contact emails
alexandre.freitas@2morrowsports.com.br

Subdomains

Subdomain
apitranslate.2morrowsports.com.br
controle-campo.2morrowsports.com.br
dashtranslate.2morrowsports.com.br
monitor-scheduler.2morrowsports.com.br
n8n.2morrowsports.com.br
netcore9.2morrowsports.com.br
www.2morrowsports.com.br

Showing 7 of 7 subdomains (7 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-113.awsdns-14.com
  • ns-951.awsdns-54.net
  • 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
  • ns-1245.awsdns-27.org
  • ns-1754.awsdns-27.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com

SPF policy

  • include: amazonses.com
  • ip: 3.212.83.50
  • ip: 34.224.211.44

Threat-feed evidence

History

Related pages

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