Skip to content

Hostname

whycatcher.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
waterloopbos b.v.
Contact emails
chris.robson@propagatorgroup.com, info@waterloopbos.nl, 2955afe7-f38b-4e41-8d8b-f62ffafd1db3@identity-protect.org, 46ae9dcf-f1cb-4db7-84d0-8c7faac61cb6@identity-protect.org, fe4b2540-20be-473c-a84c-f43412aaf82d@identity-protect.org, kwainwright@jigsaw-research.co.uk

Subdomains

Subdomain
ai.whycatcher.com
api.whycatcher.com
app.whycatcher.com
demo-api.whycatcher.com
dev-api.whycatcher.com
dev-app.whycatcher.com
dev.whycatcher.com
www-dev.whycatcher.com
www.whycatcher.com

Showing 9 of 10. 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-327.awsdns-40.com
  • ns-515.awsdns-00.net
  • ns-1308.awsdns-35.org
  • ns-1595.awsdns-07.co.uk

MX records

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com

SPF policy

  • include: amazonses.com
  • include: email.freshdesk.com
  • include: eu._netblocks.mimecast.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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