Hostname
aschnepf.com
Last fetched
aschnepf.com resolves to 93.197.147.28, announced in 93.192.0.0/10 by DTAG - Deutsche Telekom AG in DE. aschnepf.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
- 93.197.147.28
93.192.0.0/10 · DTAG - Deutsche Telekom AG · Oberursel, DE
- 93.197.154.189
93.192.0.0/10 · DTAG - Deutsche Telekom AG · Friedrichsdorf, DE
- 93.197.158.206
93.192.0.0/10 · DTAG - Deutsche Telekom AG · Friedrichsdorf, DE
- 79.194.39.207
79.192.0.0/10 · DTAG - Deutsche Telekom AG · Bad Homburg, DE
- 79.194.46.101
79.192.0.0/10 · DTAG - Deutsche Telekom AG · Königstein im Taunus, DE
- 93.197.150.187
93.192.0.0/10 · DTAG - Deutsche Telekom AG · Frankfurt am Main, DE
- 79.194.38.216
79.192.0.0/10 · DTAG - Deutsche Telekom AG · Frankfurt am Main, DE
- 84.131.119.227
IPv6 resolution
No AAAA record for aschnepf.com is recorded in WhisperGraph.
Attribution
deutsche telekom
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1327
- Registrant organisation
- registration privacy, no-ip.com
- Contact emails
- 039b316f5046e6d4-378427@privacy.no-ip.com, 0f1b6c006d589455-378427@privacy.no-ip.com, 1e8485ef33270593-378427@privacy.no-ip.com, 1f80dd1089750fea-378427@privacy.no-ip.com, 2287af2a86123ebe-378427@privacy.no-ip.com, 568c873a63c6f429-378427@privacy.no-ip.com, 6c2b7003bddb7af9-378427@privacy.no-ip.com, af504f02823ee90d-378427@privacy.no-ip.com, c3b8361fa02eb5f0-378427@privacy.no-ip.com, d13bbb4f765b182d-378427@privacy.no-ip.com, eb897684de02abcd-378427@privacy.no-ip.com, f039a2acfa643720-378427@privacy.no-ip.com, f9833d2916718d03-378427@privacy.no-ip.com
Mail and authentication
Nameservers
- ns1.no-ip.com
- ns2.no-ip.com
- ns3.no-ip.com
- ns4.no-ip.com
- ns5.no-ip.com
MX records
- mail1.no-ip.com
- mail2.no-ip.com
Threat-feed evidence
History
Related pages
Pivot from aschnepf.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: "aschnepf.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.