Skip to content

Hostname

teamappadvertising.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of teamappadvertising.com owner
Contact emails
phil@warrenracing.com.au, teamappadvertising.com@domainsbyproxy.com, 0be17e05-2e49-43d6-ae32-a06ffcec9a71@identity-protect.org, 44015e61-45c2-4908-a279-f6d68845d0c2@identity-protect.org, 44491728-0856-4e52-b2b1-1ddd3cf50087@identity-protect.org, 57a50b59-5d08-42cd-a630-d16a140f6048@identity-protect.org, 9ebbfb27-61b8-4aea-93c7-a69506764f18@identity-protect.org, owner-4619378@teamappadvertising.com.whoisprivacyservice.org

Subdomains

Subdomain
www.teamappadvertising.com

Showing 1 of 1 subdomain (1 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-166.awsdns-20.com
  • ns-549.awsdns-04.net
  • ns-1180.awsdns-19.org
  • ns-1850.awsdns-39.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

Threat-feed evidence

History

Related pages

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