Skip to content

Hostname

teameda.co

Last fetched

teameda.co resolves to 16 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.

Nutrition Label

WHISPER CANON · teameda.coRouting diversity5.7/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint7.8/10canon.whisper.security/host/teameda.co

Resolution chain

teameda.co resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
16.15.177.9416.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.183.16616.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.183.25316.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.191.12616.15.184.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.194.16216.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.207.18716.15.200.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.182.104.18116.182.96.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
16.182.43.3716.182.40.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
16.182.97.2116.182.96.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
3.5.12.1333.5.12.0/23AS14618AMAZON-AES - Amazon.com, Inc.US
52.216.215.5352.216.208.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.139.21352.217.128.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.166.12552.217.160.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.196.18952.217.192.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.92.9152.217.92.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
54.231.199.5354.231.192.0/19AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

No WHOIS records are currently associated with teameda.co in WhisperGraph.

Subdomains

1 observed subdomain of teameda.co.

Subdomain
www.teameda.co

Threat posture

History

Mail and authentication

MX records

SPF policy

1 SPF mechanism authorising senders for teameda.co.

MechanismTarget
SPF_INCLUDEspf.protection.outlook.com

Related pages

Pivot deeper into the graph from teameda.co.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "teameda.co"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.