Skip to content

Hostname

computerzone.pk

Last fetched

computerzone.pk resolves to 132.148.45.208, announced in 132.148.40.0/21 by GO-DADDY-COM-LLC - GoDaddy.com, LLC in US. computerzone.pk 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 · computerzone.pkRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/computerzone.pk

Resolution chain

IPv6 resolution

No AAAA record for computerzone.pk is recorded in WhisperGraph.

Attribution

godaddy com

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for computerzone.pk. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
api.computerzone.pk
autodiscover.computerzone.pk
cpanel.computerzone.pk
demo.computerzone.pk
mail.computerzone.pk
ns1.computerzone.pk
ns2.computerzone.pk
store.computerzone.pk
testing.computerzone.pk
vps.computerzone.pk
webdisk.computerzone.pk
webmail.computerzone.pk

Showing 12 of 14. 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

Mail and authentication

Nameservers

  • ns05.domaincontrol.com
  • ns06.domaincontrol.com
  • ns2.95.74.97.host.secureserver.net
  • ns1.95.74.97.host.secureserver.net

MX records

  • computerzone.pk
  • mail.computerzone.pk

SPF policy

  • include: secureserver.net
  • a: computerzone.pk
  • mx: computerzone.pk

Threat-feed evidence

History

Related pages

Pivot from computerzone.pk 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: "computerzone.pk"})-[: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.