Skip to content

Hostname

pickzen.com

Last fetched

pickzen.com resolves to 108.139.29.122, announced in 108.139.29.0/24 by AMAZON-02 - Amazon.com, Inc. in US. pickzen.com 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

WHISPER CANON · pickzen.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/pickzen.com

Resolution chain

IPv6 resolution

No AAAA record for pickzen.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
1&1 internet
Contact emails
pickzen.com@domainsbyproxy.com, 1273f7901e214cbd8776c766043009eb.protect@whoisguard.com, 4fd162298ac446d1bbcc3516117a64c2.protect@withheldforprivacy.com, privacy@1and1.es, contact@privacyprotect.org

Subdomains

Subdomain
admin.pickzen.com
cdn-us.pickzen.com
events.pickzen.com
help.pickzen.com
inst.pickzen.com
staging-mag1.pickzen.com
staging-mag2.pickzen.com
staging-prest.pickzen.com
staging-woo.pickzen.com
www-staging.pickzen.com
www.pickzen.com

Showing 11 of 11 subdomains (11 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-77.awsdns-09.com
  • ns-735.awsdns-27.net
  • ns-1047.awsdns-02.org
  • ns-1780.awsdns-30.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

Pivot from pickzen.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: "pickzen.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 20

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