Hostname
dns40.com
Last fetched
dns40.com resolves to 1 IPv4 address operated by AS16276 in CA. WHOIS lists iana:3862 as the registrar.
Nutrition Label
Resolution chain
dns40.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 51.79.17.52 | 51.79.0.0/17 | AS16276 | — | CA |
WHOIS identity
- Registrar
- iana:3862
- Organization
- jian xing bo
- Contact emails
Subdomains
57 observed subdomains of dns40.com.
Showing 25 of 57. View all subdomains →
Threat posture
History
Mail and authentication
MX records
SPF policy
42 SPF mechanisms authorising senders for dns40.com.
| Mechanism | Target |
|---|---|
| SPF_A | dns40.com |
| SPF_IP | 135.148.143.176/32 |
| SPF_IP | 135.148.143.211/32 |
| SPF_IP | 135.148.145.169/32 |
| SPF_IP | 144.217.117.29/32 |
| SPF_IP | 144.217.183.22/32 |
| SPF_IP | 149.56.176.64/30 |
| SPF_IP | 15.235.0.129/32 |
| SPF_IP | 15.235.105.186/32 |
| SPF_IP | 158.69.137.8/30 |
| SPF_IP | 158.69.138.40/30 |
| SPF_IP | 158.69.246.105/32 |
| SPF_IP | 167.114.173.222/32 |
| SPF_IP | 167.114.86.152/29 |
| SPF_IP | 192.99.132.24/30 |
| SPF_IP | 192.99.147.218/32 |
| SPF_IP | 192.99.148.11/32 |
| SPF_IP | 192.99.18.84/32 |
| SPF_IP | 192.99.215.76/32 |
| SPF_IP | 192.99.252.244/30 |
| SPF_IP | 192.99.85.240/30 |
| SPF_IP | 198.27.99.28/30 |
| SPF_IP | 198.50.175.168/30 |
| SPF_IP | 198.50.211.0/30 |
| SPF_IP | 198.50.211.236/30 |
| SPF_IP | 198.50.230.236/30 |
| SPF_IP | 51.222.241.108/32 |
| SPF_IP | 51.222.73.251/32 |
| SPF_IP | 54.39.173.34/32 |
| SPF_IP | 54.39.173.36/32 |
| SPF_IP | 54.39.173.38/32 |
| SPF_IP | 54.39.173.41/32 |
| SPF_IP | 54.39.202.135/32 |
| SPF_IP | 54.39.73.121/32 |
| SPF_IP | 54.39.73.124/32 |
| SPF_IP | 54.39.73.127/32 |
| SPF_IP | 54.39.73.132/32 |
| SPF_IP | 54.39.73.157/32 |
| SPF_IP | 54.39.73.180/32 |
| SPF_IP | 66.70.223.12/30 |
| SPF_IP | 66.70.255.3/32 |
| SPF_MX | dns40.com |
Related pages
Pivot deeper into the graph from dns40.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "dns40.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.