Skip to content

Hostname

yaypay.com

Last fetched

yaypay.com resolves to 151.101.1.91, announced in 151.101.0.0/22 by FASTLY - Fastly, Inc. in CA. yaypay.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 · yaypay.comRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/yaypay.com

Resolution chain

IPv6 resolution

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

Attribution

Fastly

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Contact emails
********@*****.***, admin@yaypay.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-469.awsdns-58.com
  • ns-650.awsdns-17.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1146.awsdns-15.org
  • ns-1879.awsdns-42.co.uk

MX records

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

SPF policy

  • include: _spf.google.com
  • include: eu._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • ip: 151.101.1.91
  • ip: 151.101.129.91
  • ip: 151.101.193.91
  • ip: 151.101.65.91
  • ip: 52.49.216.222

Threat-feed evidence

History

Related pages

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