Hostname
pertwk.com
Last fetched
pertwk.com resolves to 104.21.78.252, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. pertwk.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
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1479
- Registrant organisation
- bahrouz hassan
- Contact emails
- c5mk23t4noi4m9bhcf768chmfp@domaindiscreet.com, bahrouz@tiscali.dk, pwp-241114e06d897ff2e06c3ef44d85d492@privacyguardian.org, 017dd64c42538fd7cfdaa736005cbeb56ad84fa516a93168af1f007beb572414@pertwk.com.whoisproxy.org, 08a9b8e6dd295eb9a47f24d9d2ca5be545444b3a3ffefc61e36e7b675d59a85e@pertwk.com.whoisproxy.org, 19ceed208149b5232f4e9aa76a73e4fa329fdfe874ee10db3cf3edba612db3c0@pertwk.com.whoisproxy.org, 29120eb171b6d5b2b7639f4bb2e9ac7346db9ea1b13bd32849d53f9bf38048a6@pertwk.com.whoisproxy.org, a6e787eddb4a7ae52f4b5f4558cd93cf5b3c963db2814f1453f839ca1ee1a6ca@pertwk.com.whoisproxy.org, b36d89db4498ff677175a7822a354700eda64e8f37e4e6a62cbcf1442c32a4d5@pertwk.com.whoisproxy.org, e101584dcba20e473471b0732714036bb88f4e453f4d509cd6551b10e3ca49c2@pertwk.com.whoisproxy.org, f3f0185ea7640c17c5867308f6b81bf85ca4a415ae6c02c879a8819af074ca52@pertwk.com.whoisproxy.org, f80a7a0790697bf21df650d9e213ac6462ba27d83e3fd3acb57bd98894337a30@pertwk.com.whoisproxy.org, fff36eeda05363162cd05fb404aa1f6c4eab6b10ff993901ae630702e46b8da3@pertwk.com.whoisproxy.org
Subdomains
Showing 4 of 5. View all subdomains →
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
- aida.ns.cloudflare.com
- bob.ns.cloudflare.com
- ns1.dnsowl.com
- ns2.dnsowl.com
- ns3.dnsowl.com
Threat-feed evidence
History
Related pages
Pivot from pertwk.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: "pertwk.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.