Hostname

pks.zone

Last fetched Tue, 15 Sep 2026 08:02:32 GMT

pks.zone resolves to 109.250.0.110, announced in 109.250.0.0/18 by VERSATEL - 1&1 Versatel GmbH in DE. pks.zone is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

109.250.0.110
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.0.135
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.0.198
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.0.234
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.0.41
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.1.169
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Hünfeld, DE
109.250.1.224
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Hünfeld, DE
109.250.1.236
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Hünfeld, DE
109.250.1.98
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Hünfeld, DE
109.250.2.62
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Eichenzell, DE
109.250.3.132
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.3.169
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.0.31
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH · Frankfurt am Main, DE
109.250.3.146
109.250.0.0/18 · VERSATEL - 1&1 Versatel GmbH

IPv6 resolution

Attribution

versatel

ORIGIN_AS

WHOIS identity

Registrar: iana:1910

Subdomains

Subdomain
access.pks.zone
bsb.pks.zone
fw001.pks.zone
osb.pks.zone
status.pks.zone

Showing 5 of 6. View all subdomains →

Mail and authentication

Nameservers

arnold.ns.cloudflare.com
liz.ns.cloudflare.com

Threat-feed evidence

History

Pivot from pks.zone 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: "pks.zone"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.