Hostname
blox.ink
Last fetched
blox.ink resolves to 192.64.119.25, announced in 192.64.119.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. blox.ink is listed by 2 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 2 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:55:27 GMT
- Last seen on a feed
- Mon, 14 Sep 2026 00:15:52 GMT
Nutrition Label
Resolution chain
- 192.64.119.25
192.64.119.0/24 · NAMECHEAP-NET - Namecheap, Inc. · Atlanta, US
- 3.93.136.104
3.80.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.45.112.21
52.44.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.172.195.72
54.172.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.210.96.249
54.210.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.84.55.76
54.84.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.193.239.196
32.192.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for blox.ink is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- privacy service provided by withheld for privacy ehf
- Contact emails
- stephen@martiros.com
Subdomains
| Subdomain |
|---|
| www.blox.ink |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- dns1.registrar-servers.com
- dns2.registrar-servers.com
- nspx1.roblox.com
- a.misconfigured.dns.server.invalid
- nspx2.roblox.net
- nspx4.roblox.co.uk
- nspx3.roblox.us
MX records
- 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 blox.ink 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: "blox.ink"})-[: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.