Found 32 IFCICO Enabled Nodes
| Node Address | Hostname | Version | Location | Last Tested | Actions |
|---|---|---|---|---|---|
| 2:5000/111 | byte.nsk.su | Taurus 5.114.2013.19/Winter |
Novosibirsk, RU
Novotelecom Ltd |
2026-04-10 16:29 | |
| 2:5053/56 | lone-star-station.linkpc.net | Radius 4.011/24.10.2013,17:38(Bzdeta) |
Moscow, RU
Limited Liability Company "TTK-Svyaz" |
2026-04-10 16:28 | |
| 1:2320/105 | capitolcityonline.net | ifcico 2.14-tx8.10 |
Frankfort, US
Frankfort Plant Board |
2026-04-10 16:28 | |
| 1:320/319 | mbsedev.bnbbbs.net | mbcico 1.1.7.2 |
Groton, US
Comcast Cable Communications, LLC |
2026-04-10 16:28 | |
| 3:712/848 | ftn.sysgod.org | Argus 3.210 |
Sydney, AU
iiNet Limited |
2026-04-10 16:28 | |
| 2:2448/4000 | fido.softeq.org | Radius 4.010/21.01.2005,13:56(Final-Release) |
Recklinghausen, DE
Deutsche Telekom AG |
2026-04-10 16:28 | |
| 2:5026/15 | 109.60.151.138 | T-Mail 2608.NT/TCP/IP/Noncommercial |
Ivanovo, RU
Ivtelecom Ltd |
2026-04-10 13:57 | |
| 2:5023/24 | wfido.ru | T-Mail 2608.NT/TCP/IP/Noncommercial |
Kaluga, RU
KLGELECS |
2026-04-10 12:28 | |
| 2:5020/400 | ddt.demos.su | ifcico 2.15dev5.4 |
Moscow, RU
Reliable Communications s.r.o. |
2026-04-10 12:10 | |
| 1:320/219 | phoenix.bnbbbs.net | mbcico 1.1.7.2 |
Groton, US
Comcast Cable Communications, LLC |
2026-04-10 09:07 | |
| 2:2448/401 | fido.softeq.org | Radius 4.010/21.01.2005,13:56(Final-Release) |
Recklinghausen, DE
Deutsche Telekom AG |
2026-04-10 02:01 | |
| 2:463/877 | bbs.ncc.org.ua | Radius 4.010/21.01.2005,13:56(Final-Release) |
Kyiv, UA
Netassist International EOOD |
2026-04-10 02:01 | |
| 2:331/51 | bbs.bofh.it | ifcico 2.14-tx8.10 |
Milan, IT
SEEWEB s.r.l. |
2026-04-10 02:01 | |
| 2:291/10 | net291.fidonode.be | Radius 4.010/21.01.2005,13:56(Final-Release) |
Brussels, BE
OVH SAS |
2026-04-09 14:44 | |
| 2:291/111 | net291.fidonode.be | Radius 4.010/21.01.2005,13:56(Final-Release) |
Brussels, BE
OVH SAS |
2026-04-09 14:43 | |
| 2:291/1 | net291.fidonode.be | Radius 4.010/21.01.2005,13:56(Final-Release) |
Brussels, BE
OVH SAS |
2026-04-09 11:12 | |
| 2:5023/12 | 62.148.154.95 | T-Mail 2607.NT/TCP/IP/Noncommercial |
Kaluga, RU
KLGELECS 2 |
2026-04-08 18:06 | |
| 2:5025/12 | f12.n5025.ru | T-Mail 2608.NT/TCP/IP/Noncommercial |
Voronezh, RU
Informsvyaz-Chernozemye |
2026-04-08 17:22 | |
| 2:5020/2065 | f2065.no-ip.org | Taurus 5.114.2013.19/Winter/FastMM 4.991/DEBUG |
Moscow, RU
NCNET |
2026-04-08 16:25 | |
| 2:5030/976 | f976.ru | T-Mail 2608.NT/TCP/IP/Noncommercial |
Moscow, RU
MegaFon |
2026-04-08 16:09 | |
| 2:5020/806 | fido.r2akt.ru | T-Mail 2608.NT/TCP/IP/Noncommercial |
Moscow, RU
Information and Communication Technologies LLC |
2026-04-08 11:53 | |
| 2:4651/777 | f777.n4651.moiseyev.net | ifcico 2.15 |
Brovary, UA
Zeonbud LLC |
2026-04-08 04:50 | |
| 2:201/137 | scbbs.nsupdate.info | ifcico 2.14-tx8.10 |
Stockholm, SE
TELE2-BROADBAND |
2026-04-08 04:46 | |
| 2:2448/400 | fido.softeq.org | Radius 4.010/21.01.2005,13:56(Final-Release) |
Recklinghausen, DE
Deutsche Telekom AG |
2026-04-08 01:55 | |
| 2:5025/2 | f2.n5025.ru | T-Mail 2607.OS2/TCP/IP/Noncommercial |
Voronezh, RU
Informsvyaz-Chernozemye |
2026-04-08 01:49 | |
| 1:1/119 | mbsedev.bnbbbs.net | mbcico 1.1.7.2 |
Groton, US
Comcast Cable Communications, LLC |
2026-04-07 21:23 | |
| 2:5058/104 | math.ydns.eu | qico 0.59.1 |
Prague, CZ
SmartApe OU |
2026-04-07 21:08 | |
| 2:423/120 | bbs.alecoexp.cz | T-Mail 2608.NT/TCP/IP/Noncommercial |
Mnichovice, CZ
UVTnet |
2026-04-07 19:23 | |
| 1:1/19 | ftsc.bnbbbs.net | mbcico 1.1.7.2 |
Groton, US
Comcast Cable Communications, LLC |
2026-04-07 15:46 | |
| 2:423/81 | fido.bajer.cz | T-Mail 2608.OS2/TCP/IP/C50 |
Prague, CZ
Vodafone Czech Republic |
2026-04-07 03:54 | |
| 2:467/70 | f70n467.asuscomm.com | T-Mail 2608.NT/TCP/IP/Noncommercial |
Odesa, UA
TeNeT Networking Centre |
2026-04-04 14:35 | |
| 1:114/485 | bbs.trod.org | mbcico 1.0.7.22-ksb |
Cedar Knolls, US
Akamai Technologies, Inc. |
2026-04-01 08:20 |
Note: This report shows nodes that have been successfully tested with IFCICO protocol over the last 30 days. IFCICO is a traditional FidoNet mailer protocol.
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.