Hostname
ptchan.org
Last fetched
ptchan.org resolves to 104.219.235.22, announced in 104.219.235.0/24 by DATAWAGON - DataWagon LLC in US. ptchan.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.219.235.22
104.219.235.0/24 · DATAWAGON - DataWagon LLC · Buffalo, US
- 147.45.51.236
147.45.51.0/24 · GCS-AS - GLOBAL CONNECTIVITY SOLUTIONS LLP · Milan, IT
- 166.1.18.53
166.1.18.0/24 · ASNET - Baxet Group Inc. · Los Angeles, US
- 172.93.215.129
172.93.215.0/24 · DATAWAGON - DataWagon LLC · Buffalo, US
- 185.76.243.103
185.76.243.0/24 · GCS-AS - GLOBAL CONNECTIVITY SOLUTIONS LLP · Amsterdam, NL
- 194.42.206.58
194.42.206.0/23 · TRUNKNETWORKS-AS - Trunk Networks LTD · Seattle, US
- 2.59.163.158
2.59.163.0/24 · GCS-AS - GLOBAL CONNECTIVITY SOLUTIONS LLP · Warsaw, PL
- 38.135.54.232
38.135.54.0/24 · ASNET - Baxet Group Inc. · Atlanta, US
IPv6 resolution
Attribution
datawagon
ORIGIN_AS
WHOIS identity
- Registrar
- iana:638
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- owner@ptchan.org.whoisproxy.org
Subdomains
| Subdomain |
|---|
| shop.ptchan.org |
| www.ptchan.org |
Showing 2 of 3. 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
- ns2.basedns.cloud
- ns1.basedns.net
- 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
- ns3.basedns.services
MX records
- mx.zoho.eu
- mx2.zoho.eu
- mx3.zoho.eu
SPF policy
- include: zohomail.eu
Threat-feed evidence
History
Related pages
Pivot from ptchan.org 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: "ptchan.org"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.