Hostname
cd.ningposkidi.com
Last fetched
cd.ningposkidi.com resolves to 172.241.53.101, announced in 172.241.53.0/24 by SERVERS-COM - Servers.com, Inc. in NL. cd.ningposkidi.com 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
- 172.241.53.101
172.241.53.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 172.241.53.110
172.241.53.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 172.241.53.157
172.241.53.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 172.241.53.29
172.241.53.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 172.241.53.69
172.241.53.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 172.241.53.93
172.241.53.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 172.255.106.117
- 172.255.106.134
- 172.255.106.213
- 172.255.106.29
- 172.255.106.53
- 188.42.138.213
- 188.42.241.109
- 188.42.241.189
- 188.42.241.221
- 188.42.241.29
- 23.109.253.109
23.109.253.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 23.109.253.230
23.109.253.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 23.109.253.37
23.109.253.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
- 23.109.253.53
23.109.253.0/24 · SERVERS-COM - Servers.com, Inc. · Amsterdam, NL
IPv6 resolution
No AAAA record for cd.ningposkidi.com is recorded in WhisperGraph.
Attribution
com
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cd.ningposkidi.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns-281.awsdns-35.com
- ns-699.awsdns-23.net
- ns-1030.awsdns-00.org
- ns-1965.awsdns-53.co.uk
Threat-feed evidence
History
Related pages
Pivot from cd.ningposkidi.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: "cd.ningposkidi.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.