Hostname
ritzslots.com
Last fetched
ritzslots.com resolves to 104.26.4.188, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ritzslots.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.26.4.188
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.5.188
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 13.32.205.129
13.32.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 13.32.205.48
13.32.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 13.32.205.73
13.32.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 13.32.205.81
13.32.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 13.33.82.127
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 13.33.82.2
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 13.33.82.76
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 13.33.82.98
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 172.67.74.203
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for ritzslots.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Subdomains
| Subdomain |
|---|
| www.ritzslots.com |
Showing 1 of 1 subdomain (1 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
- ns-300.awsdns-37.com
- lennon.ns.cloudflare.com
- shubhi.ns.cloudflare.com
- ns-696.awsdns-23.net
- ns-1174.awsdns-18.org
- ns-1615.awsdns-09.co.uk
MX records
- mail.protonmail.ch
- mailsec.protonmail.ch
SPF policy
- include: _spf.protonmail.ch
Threat-feed evidence
History
Related pages
Pivot from ritzslots.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: "ritzslots.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.