Found 18 FTP Enabled Nodes
| Node Address | Hostname | Anon Login | Location | Last Tested | Actions |
|---|---|---|---|---|---|
| 2:2/1000 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-15 19:42 | |
| 2:341/111 | bbs.hispamsx.org | Yes |
Zaragoza, ES
Amazon.com, Inc. |
2026-04-15 14:04 | |
| 2:2/1002 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-15 00:02 | |
| 1:105/7 | digdist.synchro.net | Yes |
Beaverton, US
Wholesail networks LLC |
2026-04-14 18:05 | |
| 2:5025/150 | ftp.n5025.ru | No |
Moscow, RU
"Domain names registrar REG.RU", Ltd |
2026-04-14 16:31 | |
| 1:18/200 | bbs.outpostbbs.net | Yes |
Johnson City, US
BrightRidge |
2026-04-14 16:29 | |
| 3:712/1321 | tfb-bbs.org | No |
Brisbane, AU
Aussie Broadband |
2026-04-14 11:56 | |
| 1:396/45 | sursum-corda.com | Yes |
Huntsville, US
Comcast Cable Communications, LLC |
2026-04-14 10:38 | |
| 1:1/110 | bbs.outpostbbs.net | Yes |
Johnson City, US
BrightRidge |
2026-04-14 10:22 | |
| 2:2490/3046 | cyberia.dnsalias.com | Yes |
Bamberg, DE
Deutsche Telekom AG |
2026-04-14 09:59 | |
| 2:341/200 | bbs.zruspas.org | Yes |
Madrid, ES
RCS & RDS |
2026-04-14 08:16 | |
| 2:341/66 | bbs.zruspas.org | Yes |
Madrid, ES
RCS & RDS |
2026-04-14 06:52 | |
| 1:396/3 | sursum-corda.com | Yes |
Huntsville, US
Comcast Cable Communications, LLC |
2026-04-12 17:06 | |
| 1:342/806 | xanadubbs.ca | Yes |
Edmonton, CA
Shaw Communications |
2026-04-12 14:19 | |
| 2:2490/1500 | cyberia.dnsalias.com | Yes |
Bamberg, DE
Deutsche Telekom AG |
2026-04-12 13:23 | |
| 2:292/854 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-12 05:20 | |
| 2:292/80 | many-glacier.dyndns.org | Yes |
Antwerp, BE
Proximus |
2026-04-11 22:49 | |
| 1:266/512 | cfbbs.no-ip.com | Yes |
Bellmawr, US
Verizon Business |
2026-04-10 16:29 |
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.