Hostname
bluechipgame.com
Last fetched
bluechipgame.com resolves to 149.104.92.162, announced in 149.104.92.0/24 by LIGHT4-AS-AP - LIGHT NODE LIMITED in AR. bluechipgame.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:47 GMT
- Last seen on a feed
- Tue, 22 Sep 2026 23:26:40 GMT
Nutrition Label
Resolution chain
- 149.104.92.162
149.104.92.0/24 · LIGHT4-AS-AP - LIGHT NODE LIMITED · Buenos Aires, AR
- 172.234.24.211
172.234.16.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.57.117
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
IPv6 resolution
No AAAA record for bluechipgame.com is recorded in WhisperGraph.
Attribution
light node
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- whois privacy protection service by onamae.com
- Contact emails
- admin@bluechippokerclub.com, 35220a152fe049d8b3f943c0cc3bd75a.protect@withheldforprivacy.com, proxy@whoisprotectservice.com, reactivation-pending@mail.withheldforprivacy.com
Subdomains
| Subdomain |
|---|
| m.bluechipgame.com |
| play.bluechipgame.com |
| rcsntx.bluechipgame.com |
| wap.bluechipgame.com |
| www.bluechipgame.com |
Showing 5 of 5 subdomains (5 per page).
Mail and authentication
Nameservers
- dns1.registrar-servers.com
- dns101.registrar-servers.com
- dns102.registrar-servers.com
- dns2.registrar-servers.com
MX records
- mx.plingest.com
- eforward1.registrar-servers.com
- eforward2.registrar-servers.com
- eforward3.registrar-servers.com
- eforward4.registrar-servers.com
- eforward5.registrar-servers.com
SPF policy
- include: spf.efwd.registrar-servers.com
Threat-feed evidence
History
Related pages
Pivot from bluechipgame.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: "bluechipgame.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.