Hostname
uz-play.com
Last fetched
uz-play.com resolves to 188.114.96.3, announced in 188.114.96.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. uz-play.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
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 37.140.192.228
37.140.192.0/24 · AS-REGRU - "Domain names registrar REG.RU", Ltd · Moscow, RU
- 38.180.116.35
38.180.116.0/24 · SCALAXY-AS - Scalaxy B.V. · Amsterdam, NL
IPv6 resolution
Attribution
names reg ru
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1606
- Registrant organisation
- personal data, can not be publicly disclosed according to applicable laws.
- Contact emails
- uz-play.com@regprivate.ru
Subdomains
| Subdomain |
|---|
| mail.uz-play.com |
| www.uz-play.com |
Showing 2 of 2 subdomains (2 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
- rocket.seo-anomaly-alttext.online
- rocket.seo-anomaly-anchor.online
- rocket.seo-anomaly-authority.online
- rocket.seo-anomaly-backlink.online
- rocket.seo-anomaly-black.online
- rocket.seo-anomaly-bounce.online
- rocket.seo-anomaly-canonical.online
- rocket.seo-anomaly-conversion.online
- rocket.seo-anomaly-crawlbudget.online
- rocket.seo-anomaly-crawling.online
Mail and authentication
Nameservers
- darl.ns.cloudflare.com
- marissa.ns.cloudflare.com
- ns1.hosting.reg.ru
- ns2.hosting.reg.ru
- vip216.hosting.reg.ru
MX records
- mx1.hosting.reg.ru
- mx2.hosting.reg.ru
SPF policy
- a: uz-play.com
- mx: uz-play.com
- include: _spf.hosting.reg.ru
- ip: 37.140.192.228
Threat-feed evidence
History
Related pages
Pivot from uz-play.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: "uz-play.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.