Hostname
pagaya.com
Last fetched
pagaya.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. pagaya.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
No IPv4 resolution is recorded for pagaya.com in WhisperGraph.
IPv6 resolution
No AAAA record for pagaya.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of pagaya.com owner
- Contact emails
- pagaya.com@namebrightprivacy.com, domains@hugedomains.com, 279d7d9a-6991-4bf8-be49-7b1be7c15de6@identity-protect.org, 3901a896-f1df-4566-a4f8-5b4cb7713ce5@identity-protect.org, 916f22cf-17e7-4bdc-95bb-73351e67700c@identity-protect.org, a6e37df3-6bbc-48d0-85cf-ffbf5af2a7d4@identity-protect.org, e4640152-b841-4684-b9ba-02cf7c46bcff@identity-protect.org, f914497d-338c-40ef-9348-26a19861b769@identity-protect.org, owner-9498583@pagaya.com.whoisprivacyservice.org
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
Mail and authentication
Nameservers
- ns-308.awsdns-38.com
- ns-1000.awsdns-61.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-1532.awsdns-63.org
- ns-1777.awsdns-30.co.uk
MX records
- mxa-009ac001.gslb.pphosted.com
- mxb-009ac001.gslb.pphosted.com
SPF policy
- include: _spf.pagaya_com._d.easydmarc.pro
Threat-feed evidence
History
Related pages
Pivot from pagaya.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: "pagaya.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.