Skip to content

Hostname

publishpath.com

Last fetched

publishpath.com resolves to 64.89.44.97, announced in 64.89.32.0/20 by CENTURYLINK-LEGACY-SAVVIS - CenturyLink Communications, LLC in US. publishpath.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 · publishpath.comRouting diversity1.5/10Peering density6.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/publishpath.com

Resolution chain

IPv6 resolution

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

Attribution

centurylink

ORIGIN_AS

WHOIS identity

Registrar
iana:292
Registrant organisation
domain administrator
Contact emails
cgsjtgfgln@whoisprivacyprotect.com, domain-contact_ww_grp@oracle.com, lksvqtsbqp@whoisprivacyprotect.com, majorsingh@netsuite.com, nggmnrpc@whoisprivacyprotect.com, nlnkyspbkj@whoisprivacyprotect.com, qwpckylfv@whoisprivacyprotect.com, rvfrvnfcpq@whoisprivacyprotect.com, rwpglpvpkj@whoisprivacyprotect.com, tbgnlsmhm@whoisprivacyprotect.com, vsrlkhfh@whoisprivacyprotect.com, wxqjmxld@whoisprivacyprotect.com, xcqnlhsp@whoisprivacyprotect.com, xpcklmjtfm@whoisprivacyprotect.com, noreply@data-protected.net

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • a1-160.akam.net
  • a11-66.akam.net
  • a13-65.akam.net
  • a18-67.akam.net
  • ns1.p201.dns.oraclecloud.net
  • ns2.p201.dns.oraclecloud.net
  • ns3.p201.dns.oraclecloud.net
  • ns4.p201.dns.oraclecloud.net

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • include: spf.dynect.net

Threat-feed evidence

History

Related pages

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