Hostname
ping-test.net
Last fetched
ping-test.net resolves to 104.21.53.110, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ping-test.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.53.110
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.212.56
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.1
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.1
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1456
- Registrant organisation
- whois data protection sp. z o.o.
- Contact emails
- dngoqqcytuyi-r@mail.netart-registrar.com, newheihstmgd-r@mail.netart-registrar.com, ssnowsavywwp-r@mail.netart-registrar.com, doctodhsxhmj-r@mail.whoisdataprotection.com, eaardqddgadx-r@mail.whoisdataprotection.com, gfehbhgvdttn-r@mail.whoisdataprotection.com, ifkqwkpeojxm-r@mail.whoisdataprotection.com, tnvqoowudjxj-r@mail.whoisdataprotection.com, ubsfobhvmlyh-r@mail.whoisdataprotection.com, ysoufbwjhxvf-r@mail.whoisdataprotection.com, bernard@fs.net.pl
Subdomains
Showing 3 of 3 subdomains (3 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
- khloe.ns.cloudflare.com
- venkat.ns.cloudflare.com
MX records
- ispconfig.v-speed.eu
SPF policy
- a: ping-test.net
- mx: ping-test.net
- ip: 116.202.192.33
Threat-feed evidence
History
Related pages
Pivot from ping-test.net 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: "ping-test.net"})-[: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.