Skip to content

Hostname

tastyworks.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
2a7a96c0c72d44e0a5266de27086efdb.protect@whoisguard.com, 444501fcdef942e98eb8aa50d127948c.protect@withheldforprivacy.com

Subdomains

Subdomain
analytics.tastyworks.com
api.tastyworks.com
assets.tastyworks.com
cert.tastyworks.com
ch2.tastyworks.com
challenge.tastyworks.com
ciena-encryption.tastyworks.com
download.tastyworks.com
email.tastyworks.com
events.tastyworks.com
info.tastyworks.com
infra-tools.tastyworks.com

Showing 12 of 28. 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-137.awsdns-17.com
  • ns-786.awsdns-34.net
  • ns-1512.awsdns-61.org
  • ns-1636.awsdns-12.co.uk

MX records

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

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.iggroup.net

Threat-feed evidence

History

Related pages

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