Skip to content

Hostname

yeet.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
******** ******** (see notes section below on how to view unmasked data)
Contact emails
********@*****.***, domains@hugedomains.com, ryan.willis@endurance.com, 8919fc40-424a-4a98-ba65-9af289bfa4c5@identity-protect.org, aa2f8e0b-24be-459d-9ff9-8e642fcced0f@identity-protect.org

Subdomains

Subdomain
admin.yeet.com
api.yeet.com
catalyst.yeet.com
cs.yeet.com
dev.yeet.com
help.yeet.com
link.yeet.com
loadtest.yeet.com
local.yeet.com
reactor.yeet.com
stg.yeet.com
www.yeet.com

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

  • ns-231.awsdns-28.com
  • ns-964.awsdns-56.net
  • ns-1409.awsdns-48.org
  • ns-1541.awsdns-00.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: spf.mailjet.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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