Found 18 FTP Enabled Nodes
| Node Address | Hostname | Anon Login | Location | Last Tested | Actions |
|---|---|---|---|---|---|
| 2:341/66 | bbs.zruspas.org | Yes |
Madrid, ES
Digi Spain Telecom S.L.U. |
2026-04-29 23:10 | |
| 2:341/200 | bbs.zruspas.org | Yes |
Madrid, ES
Digi Spain Telecom S.L.U. |
2026-04-29 17:43 | |
| 1:396/45 | sursum-corda.com | Yes |
Tuscaloosa, US
Comcast Cable Communications, LLC |
2026-04-29 14:33 | |
| 2:2490/3046 | cyberia.dnsalias.com | Yes |
Bamberg, DE
Deutsche Telekom AG |
2026-04-29 11:33 | |
| 2:2490/1500 | cyberia.dnsalias.com | Yes |
Bamberg, DE
Deutsche Telekom AG |
2026-04-28 05:47 | |
| 1:396/3 | sursum-corda.com | Yes |
Tuscaloosa, US
Comcast Cable Communications, LLC |
2026-04-28 02:54 | |
| 2:292/854 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-28 01:49 | |
| 1:342/806 | xanadubbs.ca | Yes |
Edmonton, CA
Shaw Communications |
2026-04-28 00:14 | |
| 2:292/80 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-27 15:50 | |
| 2:341/111 | bbs.hispamsx.org | Yes |
Zaragoza, ES
Amazon.com, Inc. |
2026-04-27 10:05 | |
| 2:2/1000 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-27 03:46 | |
| 2:2/1002 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-26 15:38 | |
| 1:18/200 | bbs.outpostbbs.net | Yes |
Johnson City, US
BrightRidge |
2026-04-26 10:47 | |
| 1:1/110 | bbs.outpostbbs.net | Yes |
Johnson City, US
BrightRidge |
2026-04-26 08:15 | |
| 2:5025/150 | ftp.n5025.ru | No |
Moscow, RU
"Domain names registrar REG.RU", Ltd |
2026-04-26 05:49 | |
| 1:105/7 | digdist.synchro.net | Yes |
Beaverton, US
Wholesail networks LLC |
2026-04-26 03:44 | |
| 3:712/1321 | tfb-bbs.org | No |
Brisbane, AU
Aussie Broadband |
2026-04-26 03:44 | |
| 1:266/512 | cfbbs.no-ip.com | Yes |
Bellmawr, US
Verizon Business |
2026-04-25 18:15 |
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.