Skip to content

Hostname

pacifictowers.com

Last fetched

pacifictowers.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. pacifictowers.com is listed by 2 threat feeds; reconciled level CRITICAL.

Threat posture

60threat score (procedure-native scale)

CRITICAL

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Command-and-control

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Thu, 17 Sep 2026 11:11:36 GMT
Last seen on a feed
Tue, 22 Sep 2026 00:55:35 GMT

Nutrition Label

WHISPER CANON · pacifictowers.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/pacifictowers.com

Resolution chain

No IPv4 resolution is recorded for pacifictowers.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
pacifictowers.com@domainsbyproxy.com, office@jecoback.com

Subdomains

Subdomain
_spfm.pacifictowers.com
www.pacifictowers.com

Showing 2 of 3. View all subdomains →

Mail and authentication

Nameservers

  • ns25.domaincontrol.com
  • ns26.domaincontrol.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

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: dc-aa8e722993._spfm.pacifictowers.com

Threat-feed evidence

History

Related pages

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