Hostname
ns2.bitcoinkeyring.com
Last fetched
ns2.bitcoinkeyring.com resolves to 2 IPv4 addresses operated by AS-COLOCROSSING - HostPapa in US.
Nutrition Label
Resolution chain
ns2.bitcoinkeyring.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 192.210.169.37 | 192.210.169.0/24 | AS36352 | AS-COLOCROSSING - HostPapa | US |
| 23.95.52.187 | 23.95.52.0/24 | AS36352 | AS-COLOCROSSING - HostPapa | US |
WHOIS identity
No WHOIS records are currently associated with ns2.bitcoinkeyring.com in WhisperGraph.
Threat posture
History
Mail and authentication
MX records
SPF policy
58 SPF mechanisms authorising senders for ns2.bitcoinkeyring.com.
| Mechanism | Target |
|---|---|
| SPF_IP | 103.73.64.41 |
| SPF_IP | 103.73.64.83 |
| SPF_IP | 103.73.65.198 |
| SPF_IP | 135.125.223.190 |
| SPF_IP | 185.175.58.193 |
| SPF_IP | 185.175.58.56 |
| SPF_IP | 185.175.58.57 |
| SPF_IP | 185.175.58.65 |
| SPF_IP | 185.175.58.70 |
| SPF_IP | 194.29.100.106 |
| SPF_IP | 194.29.100.148 |
| SPF_IP | 2001:41d0:700:2ebe:102f:2174:4382:1107 |
| SPF_IP | 2001:41d0:700:2ebe:20fd:ae4c:a83:c901 |
| SPF_IP | 2001:41d0:700:2ebe:215b:42d3:de98:eb2b |
| SPF_IP | 2001:41d0:700:2ebe:254d:d2aa:bb57:fdf0 |
| SPF_IP | 2001:41d0:700:2ebe:3f98:3394:f09c:c5e2 |
| SPF_IP | 2001:41d0:700:2ebe:4298:a4cb:75e6:25e5 |
| SPF_IP | 2001:41d0:700:2ebe:4a73:2b00:b256:15bc |
| SPF_IP | 2001:41d0:700:2ebe:4d7c:b4f6:683c:548 |
| SPF_IP | 2001:41d0:700:2ebe:666c:1e0e:d526:7a71 |
| SPF_IP | 2001:41d0:700:2ebe:6e9d:1a32:aa75:8e9a |
| SPF_IP | 2001:41d0:700:2ebe:88ab:f558:92e9:53f |
| SPF_IP | 2001:41d0:700:2ebe:8a81:f948:bde5:e4e7 |
| SPF_IP | 2001:41d0:700:2ebe:91c3:35f2:e164:2e8f |
| SPF_IP | 2001:41d0:700:2ebe:9e1f:ec99:93fc:3efc |
| SPF_IP | 2001:41d0:700:2ebe:ac6:9d92:c2c3:362e |
| SPF_IP | 2001:41d0:700:2ebe:af5e:8add:6511:363a |
| SPF_IP | 2001:41d0:700:2ebe:b1c9:9071:a4fe:99ad |
| SPF_IP | 2001:41d0:700:2ebe:c573:f9ae:c83e:fae0 |
| SPF_IP | 2001:41d0:700:2ebe:de1:6306:db16:703b |
| SPF_IP | 2001:41d0:700:2ebe:f48f:ccc1:2df4:a8d2 |
| SPF_IP | 216.108.231.138 |
| SPF_IP | 216.108.231.78 |
| SPF_IP | 216.108.231.82 |
| SPF_IP | 216.108.231.86 |
| SPF_IP | 51.210.197.179 |
| SPF_IP | 51.210.197.180 |
| SPF_IP | 51.210.197.181 |
| SPF_IP | 51.210.197.185 |
| SPF_IP | 51.254.133.209 |
| SPF_IP | 51.38.153.205 |
| SPF_IP | 51.38.153.206 |
| SPF_IP | 51.75.34.190 |
| SPF_IP | 51.75.36.72 |
| SPF_IP | 51.75.60.227 |
| SPF_IP | 51.77.36.92 |
| SPF_IP | 51.77.38.210 |
| SPF_IP | 51.77.39.164 |
| SPF_IP | 54.38.221.187 |
| SPF_IP | 54.38.221.189 |
| SPF_IP | 54.38.221.190 |
| SPF_IP | 54.38.221.191 |
| SPF_IP | 57.128.243.193 |
| SPF_IP | 66.85.162.114 |
| SPF_IP | 66.85.162.115 |
| SPF_IP | 66.85.162.116 |
| SPF_IP | 66.85.162.117 |
| SPF_IP | 66.85.162.118 |
Related pages
Pivot deeper into the graph from ns2.bitcoinkeyring.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "ns2.bitcoinkeyring.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.