Found 18 FTP Enabled Nodes
| Node Address | Hostname | Anon Login | Location | Last Tested | Actions |
|---|---|---|---|---|---|
| 1:105/7 | digdist.synchro.net | Yes |
Beaverton, US
Wholesail networks LLC |
2026-04-10 18:48 | |
| 3:712/1321 | tfb-bbs.org | No |
Brisbane, AU
Aussie Broadband |
2026-04-10 17:00 | |
| 2:5025/150 | ftp.n5025.ru | No |
Moscow, RU
"Domain names registrar REG.RU", Ltd |
2026-04-10 16:30 | |
| 2:2490/3046 | cyberia.dnsalias.com | Yes |
Bamberg, DE
Deutsche Telekom AG |
2026-04-10 16:29 | |
| 1:266/512 | cfbbs.no-ip.com | Yes |
Bellmawr, US
Verizon Business |
2026-04-10 16:29 | |
| 1:18/200 | bbs.outpostbbs.net | Yes |
Johnson City, US
BrightRidge |
2026-04-10 16:28 | |
| 1:1/110 | bbs.outpostbbs.net | Yes |
Johnson City, US
BrightRidge |
2026-04-10 16:17 | |
| 2:341/66 | bbs.zruspas.org | Yes |
Madrid, ES
RCS & RDS |
2026-04-10 14:22 | |
| 1:396/45 | sursum-corda.com | Yes |
Huntsville, US
Comcast Cable Communications, LLC |
2026-04-10 10:38 | |
| 2:341/200 | bbs.zruspas.org | Yes |
Madrid, ES
RCS & RDS |
2026-04-10 08:15 | |
| 1:342/806 | xanadubbs.ca | Yes |
Edmonton, CA
Shaw Communications |
2026-04-08 21:26 | |
| 2:2490/1500 | cyberia.dnsalias.com | Yes |
Bamberg, DE
Deutsche Telekom AG |
2026-04-08 13:22 | |
| 2:292/854 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-08 11:28 | |
| 2:2/1000 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-08 04:31 | |
| 2:292/80 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-08 00:37 | |
| 2:341/111 | bbs.hispamsx.org | Yes |
Zaragoza, ES
Amazon.com, Inc. |
2026-04-07 14:03 | |
| 2:2/1002 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-07 04:23 | |
| 1:396/3 | sursum-corda.com | Yes |
Tuscaloosa, US
Comcast Cable Communications, LLC |
2026-04-04 18:59 |
Note: This report shows nodes that have been successfully tested with FTP protocol over the last 30 days. FTP is used for file distribution and downloads in the FidoNet network.
Note about Location: The "Location" column shows the geographic location determined from the node's IP address (via GeoIP lookup), not the location specified in the nodelist. This represents the actual physical location where the node's server is hosted.