Hostname
igamingtop.com
Last fetched
igamingtop.com resolves to 104.21.15.118, announced in 104.22.2.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. igamingtop.com is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:31 GMT
- Last seen on a feed
- Mon, 14 Sep 2026 23:25:39 GMT
Nutrition Label
Resolution chain
- 104.21.15.118
104.22.2.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.162.149
172.68.25.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.115.195.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.115.196.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 208.91.197.108
208.92.0.0/21 · CONFLUENCE-NETWORK-INC - Confluence Networks Inc · Road Town, VG
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1111
- Registrant organisation
- andrey skalev
- Contact emails
- erikmeijers67@hotmail.com, igamingtop.com@redacted-for-privacy.name, andreyskalev@yandex.ru
Subdomains
| Subdomain |
|---|
| admin.igamingtop.com |
| app.igamingtop.com |
| dev.igamingtop.com |
| ftp.igamingtop.com |
| mail.igamingtop.com |
| pop.igamingtop.com |
| smtp.igamingtop.com |
| www.igamingtop.com |
Showing 8 of 8 subdomains (8 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
- luke.ns.cloudflare.com
- martha.ns.cloudflare.com
- meadow.ns.cloudflare.com
- santino.ns.cloudflare.com
- sk.s7.ans1.ns58.klczy.com
- sk.s7.ans2.ns58.klczy.com
MX records
- mail.igamingtop.com
Threat-feed evidence
History
Related pages
Pivot from igamingtop.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: "igamingtop.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.