Skip to content

Hostname

ptconsumer.net

Last fetched

ptconsumer.net resolves to 103.174.152.18, announced in 103.174.152.0/24 by COLOCONE1-AS-AP - ColoCone in BD. ptconsumer.net 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 · ptconsumer.netRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/ptconsumer.net

Resolution chain

IPv6 resolution

No AAAA record for ptconsumer.net is recorded in WhisperGraph.

Attribution

colocone

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ptconsumer.net. 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
autodiscover.ptconsumer.net
cpanel.ptconsumer.net
cpcalendars.ptconsumer.net
cpcontacts.ptconsumer.net
mail.ptconsumer.net
webdisk.ptconsumer.net
webmail.ptconsumer.net
www.ptconsumer.net

Showing 8 of 8 subdomains (8 per page).

Mail and authentication

Nameservers

  • cns1.securehostingpanel.com
  • cns2.securehostingpanel.com
  • ns1.securehostingpanel.com
  • ns2.securehostingpanel.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

  • ptconsumer.net

SPF policy

  • include: relay.mailchannels.net
  • a: ptconsumer.net
  • mx: ptconsumer.net

Threat-feed evidence

History

Related pages

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