Skip to content

Hostname

prtc.net

Last fetched

prtc.net resolves to 196.28.61.113, announced in 196.28.61.0/24 by COQUI-NET - DATACOM CARIBE, INC. in PR. prtc.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 · prtc.netRouting diversity1.5/10Peering density5.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/prtc.net

Resolution chain

IPv6 resolution

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

Attribution

datacom caribe

ORIGIN_AS

WHOIS identity

Registrar
iana:9
Contact emails
02b1e9150a1612332811ad1e636e0c1f@domaindiscreet.com, 26f377170a28fd0a6b49833f6794dc71@domaindiscreet.com, 57916777@myprivatename.com, 5c38e71e0a28fd0a5f03349ee605c482@domaindiscreet.com, 67f2bc940a28fd0a1a77ae1963301953@domaindiscreet.com, 7612e3810a28fd0a3b618d30402d8bbe@domaindiscreet.com, a889384d0a28fd0a3c7b7e1f87ddbf2a@domaindiscreet.com, d7c11a1e0a28fd0a6938417723681f99@domaindiscreet.com, da236ef30a28fd0a53c8b4e4a96f65be@domaindiscreet.com, e94b53ef0a28fd0a2fe11d2a1079848b@domaindiscreet.com, f9g55srr66ht1bjquqm5o9naca@domaindiscreet.com, ff756e8d0a28fd0a3f057b06a555a4ad@domaindiscreet.com

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

  • ns1.coqui.net
  • ns2.coqui.net

MX records

  • mx1.pangia.biz
  • mx2.pangia.biz
  • mx3.pangia.biz

SPF policy

  • ip: 209.67.128.0/24
  • ip: 74.202.139.0/24
  • ip: 74.202.142.0/24
  • ip: 65.74.168.0/24
  • ip: 216.163.188.0/24
  • ip: 64.191.223.0/24
  • ip: 216.152.255.0/24
  • mx: prtc.net
  • ip: 69.26.182.10
  • ip: 69.26.182.242
  • ip: 75.4.202.4

Threat-feed evidence

History

Related pages

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