Hostname
pironet.com
Last fetched
pironet.com resolves to 195.227.75.134, announced in 195.227.0.0/16 by PIRONETNDH-AS - CANCOM Managed Services GmbH in DE. pironet.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
IPv6 resolution
No AAAA record for pironet.com is recorded in WhisperGraph.
Attribution
cancom managed
ORIGIN_AS
WHOIS identity
- Registrar
- iana:976
- Registrant organisation
- cancom managed services
- Contact emails
- i434chimlnwmst4koolhpxf7wiotmh2wbtzqq2lyqhiw4@protectedmx.com, i6h2ybccc3o53o3yqrj34pjuhsx6dkcvuy3iouqaffija@protectedmx.com, i6mfuw3iyt3kuhsh7jcvphtchz4ob3tren6bp5zq4qky6@protectedmx.com, i6oguv3itxvglhk3fhnec3dy4s43om3xb3scktqi3tt2c@protectedmx.com, i6zqf42ade7bbomg2w555nubbdqjdcpxtvdabdpascdis@protectedmx.com, ibdapyafcso7iwjg5pbb2rexz6u4tl4fhqazm42q6hqzc@protectedmx.com, idtnbmcvz6466ybjvrw72qh5mdimgl2cpupzgglanuata@protectedmx.com, imolq6qjueuhu5vhcd5qbukw7cwmcy4chus5emyiaglem@protectedmx.com, imz2jwr7prs5t7hncjhqlzqzxid22dqhwhopwvri5zzks@protectedmx.com, in4nb65esm76mpehw7v54y5ehppkoz77rzvgia6iuikd6@protectedmx.com, ipyorfhgnrlcq54isxpwjv5jatnkwscy35e3q6hatjyc2@protectedmx.com, ivdrqqpay3xv2xwrh7vcqbo4232pqhtnpp4q4wga3riqg@protectedmx.com, ivztw5dxftiorxtuuw4owduxru4ogg6q6x7trxzyhrjz4@protectedmx.com, izajjff2lqqkqw4sndvk63x2rbzp2n57mr34dc2q4qzlq@protectedmx.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- dns01.pironet-ndh.com
- dns02.pironet-ndh.com
- dns03.pironet-ndh.com
MX records
- secure-mail01.de.cancom-mase.com
- secure-mail02.de.cancom-mase.com
- secure-mail03.de.cancom-mase.com
- secure-mail04.de.cancom-mase.com
Threat-feed evidence
History
Related pages
Pivot from pironet.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: "pironet.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.