Hostname
yellowpepper.com
Last fetched
yellowpepper.com resolves to 104.18.6.128, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. yellowpepper.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
- 104.18.6.128
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.7.128
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 8.47.69.4
8.47.69.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Bratislava, SK
- 8.6.112.4
IPv6 resolution
No AAAA record for yellowpepper.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- internet domain administrator
- Contact emails
- hostmaster@visa.com, operations@yellowpepper.com
Subdomains
Showing 12 of 65. 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.
Mail and authentication
Nameservers
- henry.ns.cloudflare.com
- suzanne.ns.cloudflare.com
- 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
MX records
- portal1i.visa.com
- portal2i.visa.com
- portal3i.visa.com
- portal4i.visa.com
SPF policy
- ip: 198.241.150.0/24
- ip: 198.241.159.0/24
- ip: 198.241.162.0/24
- ip: 198.241.168.0/24
- ip: 198.241.174.0/24
- ip: 198.241.206.0/24
- ip: 198.241.207.0/24
- include: _spf.google.com
- a: yellowpepper.com
- ip: 34.139.131.4
- ip: 34.145.227.75
- ip: 34.85.131.108
- ip: 34.86.147.67
- ip: 35.236.204.117
- ip: 35.237.61.136
Threat-feed evidence
History
Related pages
Pivot from yellowpepper.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: "yellowpepper.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.