Skip to content

Hostname

williamyeoward.com

Last fetched

williamyeoward.com resolves to 104.26.14.238, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. williamyeoward.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 · williamyeoward.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/williamyeoward.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1910
Registrant organisation
on behalf of williamyeoward.com owner
Contact emails
philp@fisheyehq.com, 524d37ca-cf76-45d2-9109-d1aa7499521c@identity-protect.org, f8b4e569-b809-4317-9424-8b4eb13dd0db@identity-protect.org

Subdomains

Subdomain
mail.williamyeoward.com
staging.williamyeoward.com
trade.williamyeoward.com
www.williamyeoward.com

Showing 4 of 4 subdomains (4 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

Mail and authentication

Nameservers

  • major.ns.cloudflare.com
  • poppy.ns.cloudflare.com

MX records

  • williamyeoward-com.mail.protection.outlook.com

SPF policy

  • ip: 219.88.246.20/32
  • ip: 219.88.246.23/32
  • ip: 219.88.246.25/32
  • ip: 219.88.246.26/32
  • include: spf.protection.outlook.com
  • a: williamyeoward.com
  • mx: williamyeoward.com
  • include: sendgrid.net
  • ip: 54.78.245.38

Threat-feed evidence

History

Related pages

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