Hello, All!

I took the latest nodelist and tried to check where the nodes are physically located, based on their IP addresses. I know it's not very accurate, but...
Geolocation service: https://ip-api.com


================================================================================
FidoNet Node IP Geolocation Report ================================================================================

Total nodes with internet connectivity: 1058
Nodes with IP addresses: 66
Nodes with hostnames: 913
Successfully resolved hostnames: 871
Failed hostname resolutions: 61

----------------------------------------
Country Distribution:
----------------------------------------
Russia 270 nodes
United States 261 nodes
Germany 66 nodes
Canada 52 nodes
United Kingdom 25 nodes
The Netherlands 23 nodes
Ukraine 22 nodes
Czechia 18 nodes
Sweden 14 nodes
Belgium 14 nodes
Australia 14 nodes
Finland 13 nodes
Italy 12 nodes
New Zealand 12 nodes
Austria 11 nodes
France 11 nodes
Belarus 11 nodes
Spain 10 nodes
Switzerland 9 nodes
Argentina 8 nodes
Israel 6 nodes
Brazil 5 nodes
Estonia 4 nodes
Colombia 4 nodes
Ireland 3 nodes
Netherlands 3 nodes
Chile 3 nodes
Portugal 2 nodes
Hungary 2 nodes
Kazakhstan 2 nodes
Serbia 1 nodes
Greece 1 nodes
Cyprus 1 nodes
Poland 1 nodes
Moldova 1 nodes
Bulgaria 1 nodes
Singapore 1 nodes




Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello Dmitry,

On Thursday July 31 2025 21:33, you wrote to All:

Netherlands 3 nodes

Definitely wrong. There are 12 nodes listed in R28 and they are definitely located in The Netherlands.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Hello, Michiel!

Thursday July 31 2025 21:28, you wrote to me:

Netherlands 3 nodes

Definitely wrong. There are 12 nodes listed in R28 and they are
definitely located in The Netherlands.

Yeah, it's so sad that those 3 unlucky nodes belong to the non-existent country "Netherlands", while 22 lucky nodes belong to the well-known "The Netherlands".


role: Liberty Global RIPE DBM
address: Liberty Global B.V.
address: Boeing Avenue 53
address: 1119PE Schiphol-Rijk
address: Netherlands

role: VODAFONEZIGGO IP AUTHORITY
address: Kabelweg 51
address: 1014BA Amsterdam
address: The Netherlands

So the total number is: 22+3=25.

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hi Dmitry,

On 2025-07-31 23:13:21, you wrote to Michiel van der Vlist:

Netherlands 3 nodes

Definitely wrong. There are 12 nodes listed in R28 and they are
definitely located in The Netherlands.

Yeah, it's so sad that those 3 unlucky nodes belong to the non-existent country "Netherlands", while 22 lucky nodes belong to the well-known "The Netherlands".

23.

role: Liberty Global RIPE DBM
address: Liberty Global B.V.
address: Boeing Avenue 53
address: 1119PE Schiphol-Rijk
address: Netherlands

role: VODAFONEZIGGO IP AUTHORITY
address: Kabelweg 51
address: 1014BA Amsterdam
address: The Netherlands

That looks like the whois information. That's not a reliable way to find out what country an IP address belongs to. You should use geoiplookup.

So the total number is: 22+3=25.

23+3=26. Still a lot more then the 12 that are in the nodelist!?

Can you list the nodes your software finds located in the Netherlands?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello, Wilfred!

Thursday July 31 2025 22:48, you wrote to me:

That looks like the whois information. That's not a reliable way to
find out what country an IP address belongs to. You should use geoiplookup.

Which service, exactly? I've used ip-api.com, but most of those services rely on whois information whenever available.
Give me the website of any service with a free API and I'll use it if you think it's more accurate.

My current home IP address in Moscow resolves to the UK, but it's configured on a Mikrotik router in Germany and used for VPN connections from Russia.
No one knows that.

23+3=26. Still a lot more then the 12 that are in the nodelist!?

Sure, because many data centers are located in the Netherlands and those nodes are hosted there.

Can you list the nodes your software finds located in the Netherlands?

What for?

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hi Dmitry,

On 2025-08-01 00:21:44, you wrote to me:

That looks like the whois information. That's not a reliable way to
find out what country an IP address belongs to. You should use
geoiplookup.

Which service, exactly? I've used ip-api.com, but most of those services rely
on whois information whenever available. Give me the website of any service
with a free API and I'll use it if you think it's more accurate.

On Linux there is the GeoIP library you could use.

At https://www.ipdeny.com/ipblocks/ you can download files that list ip ranges for all countries. But you will have to write your own code around it to get a country from an IP address.

23+3=26. Still a lot more then the 12 that are in the nodelist!?

Sure, because many data centers are located in the Netherlands and those nodes
are hosted there.

Maybe...

Can you list the nodes your software finds located in the
Netherlands?

What for?

So I can check what countries are found with geoiplookup for IP's of nodes that are not in R28. To satisfy my curiosity about the mismatch. ;-)

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello, Wilfred!

Friday August 01 2025 13:40, you wrote to me:

Which service, exactly? I've used ip-api.com, but most of those
services rely on whois information whenever available. Give me
the website of any service with a free API and I'll use it if you
think it's more accurate.

On Linux there is the GeoIP library you could use.

Multiple different libraries. It's so unfortunate that I don't write Linux-only software, so I always use multiplatform libraries ;)
But the problem is not with the libraries - it's with the data they use.

At https://www.ipdeny.com/ipblocks/ you can download files that list
ip ranges for all countries. But you will have to write your own code around it to get a country from an IP address.

But you wrote that the WHOIS data is not accurate. And this is exactly the aggregated WHOIS data:
https://www.ipdeny.com/copyright.php

You've changed your mind?

My sources (https://ip-api.com/docs/legal):

-+-
We use multiple sources for populating our database, including BGP, RIR, ISP and data sharing agreements, geofeeds and latency-based tracking.
For some IP ranges we fallback to GeoLite2 data created by MaxMind, available from www.maxmind.com
-+-

Not Google's database, but still better than just WHOIS.

Sure, because many data centers are located in the Netherlands
and those nodes are hosted there.

Maybe...

With modern clouds, it's even possible to host node in multiple countries simultaneously.

So I can check what countries are found with geoiplookup for IP's of
nodes that are not in R28. To satisfy my curiosity about the mismatch.
;-)

Just checking if there's no hidden agenda ;)

From my local copy (it's 2 days old):

*Germany is on the list because 1 node has 2 hostnames and one of them is in Germany.

==== Begin "NL.txt" ====
Loaded 675 cached IP geolocations from ip_geolocation_cache.pkl
Fetching nodes with internet connectivity...
Using latest nodelist from 2025-07-30
Found 1058 nodes with internet connectivity

Analyzing IP addresses and geolocations...

Found 998 host entries from 973 nodes

Resolving 697 unique hostnames...

Processing 652 unique IP addresses:
- 645 already in cache
- 7 need API lookup

Getting geolocation for 7 uncached IP addresses...
Processing batch 1/1
Saved 682 IP geolocations to cache

================================================================================
FidoNet Node IP Geolocation Report
Filtered by Country: NL ================================================================================

Nodes in NL: 26
Nodes with IP addresses: 66
Nodes with hostnames: 913
Successfully resolved hostnames: 873
Failed hostname resolutions: 59

----------------------------------------
Country Distribution for NL:
----------------------------------------
The Netherlands 23 nodes
Netherlands 3 nodes
Germany 1 nodes

----------------------------------------
Node Details for NL:
----------------------------------------

Node 1:275/91 - Fluph
Sysop: Leslie_Given
Location: Elkview_WV
Hostname: fluph.zapato.org -> 5.39.216.238
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Hostkey B.V.

Node 1:275/92 - Fluph_test
Sysop: Leslie_Given
Location: Elkview_WV
Hostname: fluph.zapato.org -> 5.39.216.238
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Hostkey B.V.

Node 1:275/94 - pure_fluph
Sysop: Leslie_Given
Location: Elkview_WV
Hostname: fluph.zapato.org -> 5.39.216.238
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Hostkey B.V.

Node 2:28/0 - Nederland
Sysop: Kees_van_Eeten
Location: NL
Hostname: fido.ddutch.nl -> 77.174.211.43
Country: The Netherlands (NL)
Region: North Holland, City: Purmerend
ISP: Concepts ICT B.V

Node 2:280/0 - Nederland(210)
Sysop: Kees_van_Eeten
Location: Heerhugowaard
Hostname: fido.ddutch.nl -> 77.174.211.43
Country: The Netherlands (NL)
Region: North Holland, City: Purmerend
ISP: Concepts ICT B.V

Node 2:280/464 - FMail_DEV_fka_AOBL
Sysop: Wilfred_van_Velzen
Location: Lisse
Hostname: fmailhq.fidoweb.net -> 45.83.243.76
Country: Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Freedom Internet BV

Node 2:280/1049 - The_Coast
Sysop: Simon_Voortman
Location: NL
Hostname: thecoastbbs.nl -> 87.195.129.44
Country: The Netherlands (NL)
Region: North Holland, City: Beverwijk
ISP: Solcon Internetdiensten B.V

Node 2:280/1203 - Randstad
Sysop: Frank_de_Bruijn
Location: NL
Hostname: randstad.aconet.org -> 83.86.249.40
Country: The Netherlands (NL)
Region: South Holland, City: The Hague
ISP: ZIGGO

Node 2:280/1208 - UniCorn
Sysop: Henri_Derksen
Location: Arnhem
IP: 77.174.89.46
Country: The Netherlands (NL)
Region: South Holland, City: Delft
ISP: Concepts ICT B.V.

Node 2:280/2000 - Alcatrash
Sysop: Michael_Trip
Location: Apeldoorn
Hostname: fido.alcatrash.org -> 84.87.244.28
Country: The Netherlands (NL)
Region: Gelderland, City: Apeldoorn
ISP: KPN B.V.

Node 2:280/2030 - Westland_BBS
Sysop: Martien_Korenblom
Location: Hoek_van_Holland
Hostname: bbs.korenblom.nl -> 136.144.237.181
Country: The Netherlands (NL)
Region: Gelderland, City: Doorwerth
ISP: TransIP BV

Node 2:280/2040 - Magic_Systems
Sysop: Leo_Barnhoorn
Location: Katwijk
Hostname: bbs.magic-systems.net -> 86.88.76.77
Country: The Netherlands (NL)
Region: South Holland, City: Katwijk
ISP: KPN B.V.

Node 2:280/2050 - Postbus_7
Sysop: Floris_van_Unen
Location: Nieuw-Vennep
Hostname: fido.unen.net -> 40.119.129.60
Country: Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Microsoft Corporation

Node 2:280/2060 - AroundMyRoom's_Mailer
Sysop: Dennis_Slagers
Location: Apeldoorn
Hostname: fidonet.aroundmyroom.com -> 213.93.173.212
Country: The Netherlands (NL)
Region: Gelderland, City: Apeldoorn
ISP: Vodafone Ziggo

Node 2:280/5003 - Double_Dutch
Sysop: Kees_van_Eeten
Location: Heerhugowaard
Hostname: fido.ddutch.nl -> 77.174.211.43
Country: The Netherlands (NL)
Region: North Holland, City: Purmerend
ISP: Concepts ICT B.V

Node 2:280/5555 - Nieuw_Schnoord
Sysop: Michiel_van_der_Vlist
Location: Driebergen
Hostname: fido.vlist.eu -> 83.80.243.26
Country: The Netherlands (NL)
Region: Utrecht, City: Driebergen-Rijsenburg
ISP: Vodafone Ziggo
Hostname: fido4to6.vlist.eu -> 185.248.148.18
Country: Germany (DE)
Region: Hesse, City: Frankfurt am Main
ISP: Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG

Node 2:5015/120 - Yurik_Station
Sysop: Yuriy_Hashev
Location: Nizhny_Novgorod
Hostname: v1145709.hosted-by-vdsina.ru -> 77.246.105.33
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Servers Tech Fzco

Node 2:5019/400 - GaNJaNET_STaTi0N_II
Sysop: Konstantin_Kuzov
Location: Smolensk
Hostname: fido.g0x.ru -> 5.255.103.168
Country: The Netherlands (NL)
Region: Flevoland, City: Dronten
ISP: The Infrastructure Group B.V.

Node 2:5020/828 - f828.n5020.z2.binkp.net
Sysop: Kirill_Temnenkov
Location: Moscow
Hostname: f828.n5020.z2.binkp.net -> 185.162.130.189
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Hosting purposes in NL

Node 2:5020/837 - Night_BBS
Sysop: Kirill_Kaplin
Location: Moscow
Hostname: nightbbs.ru -> 89.150.34.50
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Clodo Cloud Service CO. L.L.C

Node 2:5030/3165 - The_Death_Of_Fire_Station
Sysop: Serg_Podtynnyi
Location: St.Petersburg
Hostname: fidonet.podtynnyi.com -> 178.128.142.33
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: DigitalOcean, LLC

Node 2:5031/25 - BBBBs
Sysop: Alex_Kazankov
Location: Murmansk
Hostname: fido.x86.su -> 185.125.230.67
Country: Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: xorek.cloud International LTD

Node 2:5034/0 - KosNet
Sysop: Vladimir_Bobarykin
Location: Kostroma
Hostname: fido.cryptonets.ru -> 185.247.18.40
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Timeweb, LLP

Node 2:5034/13 - Last_Station
Sysop: Vladimir_Bobarykin
Location: Kostroma
Hostname: fido.cryptonets.ru -> 185.247.18.40
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: Timeweb, LLP

Node 2:5053/42 - ALT(r)_Co.
Sysop: Aleksey_Tolmatsky
Location: Saratov_Russia
Hostname: altrco.hopto.org -> 195.246.110.223
Country: The Netherlands (NL)
Region: North Holland, City: Amsterdam
ISP: 365.partners INC

Node 4:801/201 - Clube_da_Insonia_BBS
Sysop: Glauber_Rodrigues
Location: Santo_Andre_SP
Hostname: bbs.conf.eti.br -> 194.5.159.64
Country: The Netherlands (NL)
Region: Drenthe, City: Meppel
ISP: Hostinger International Limited
==== End "NL.txt" ====


Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello Dmitry,

On Friday August 01 2025 15:04, you wrote to Wilfred van Velzen:

*Germany is on the list because 1 node has 2 hostnames and one of
them is in Germany.

That wouldn't be me would it?

Node 2:280/5555 - Nieuw_Schnoord
Sysop: Michiel_van_der_Vlist
Location: Driebergen
Hostname: fido.vlist.eu -> 83.80.243.26
Country: The Netherlands (NL)
Region: Utrecht, City: Driebergen-Rijsenburg
ISP: Vodafone Ziggo

You missed the second part. fido.vlist.eu has two A and two AAAA records. I am multi homed, one connection with Ziggo via coax and one connection to Delta via ftth.

Hostname: fido4to6.vlist.eu -> 185.248.148.18
Country: Germany (DE)
Region: Hesse, City: Frankfurt am Main
ISP: Michael Sebastian Schinzel trading as IP-Projects GmbH & Co.

That must be confusing for those not not having read my Fidonews articles about my DS-Lite emulation experiments. My binkp server is located at my home in Driebergen NL. The German IPv4 adres points to the V4 to V6 port mapper of feste-ip.net. It is a relic of my DS-Lite emulation experiments.

FN 34:31 Jul 2017 DS-Lite emulation experiment v2.0
FN 34:37 Sep 2017 DS-Lite emulation experiment 2.0, the results
FN 34:33 Aug 2017 DS-Lite: a solution
FN 34:38 Sep 2017 DS-Lite Emulation experiment v2.1


BTW, I am not the only node in Fidonet that is dual homed...

BTW2 You missed 280/5006 becasue you dit not check for IPv6. 280/5006 is IPv6 only.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Hello, Michiel!

Friday August 01 2025 19:58, you wrote to me:

*Germany is on the list because 1 node has 2 hostnames and one
of them is in Germany.

That wouldn't be me would it?

It depends on who's running the investigation and doing the questioning.

Node 2:280/5555 - Nieuw_Schnoord
Sysop: Michiel_van_der_Vlist
Location: Driebergen
Hostname: fido.vlist.eu -> 83.80.243.26
Country: The Netherlands (NL)
Region: Utrecht, City: Driebergen-Rijsenburg
ISP: Vodafone Ziggo

You missed the second part. fido.vlist.eu has two A and two AAAA
records. I am multi homed, one connection with Ziggo via coax and one connection to Delta via ftth.

Those details are not important for this report. But very important for my other projects.
Please keep your multi homed setup running for several months. Thank you.

That must be confusing for those not not having read my Fidonews
articles about my DS-Lite emulation experiments. My binkp server is located at my home in Driebergen NL. The German IPv4 adres points to
the V4 to V6 port mapper of feste-ip.net. It is a relic of my DS-Lite emulation experiments.

The Germans would probably call it "Das Experiment".

BTW, I am not the only node in Fidonet that is dual homed...

Happy to hear that!

BTW2 You missed 280/5006 becasue you dit not check for IPv6. 280/5006
is IPv6 only.

He is from "Heerhugowaard". I can't even pronounce that.

"Heer" in Russian means "penis", BTW.

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello Dmitry,

On Friday August 01 2025 22:44, you wrote to me:

*Germany is on the list because 1 node has 2 hostnames and one
of them is in Germany.

That wouldn't be me would it?

It depends on who's running the investigation and doing the
questioning.

You run the application, I ask the question.

Node 2:280/5555 - Nieuw_Schnoord
Sysop: Michiel_van_der_Vlist
Location: Driebergen
Hostname: fido.vlist.eu -> 83.80.243.26
Country: The Netherlands (NL)
Region: Utrecht, City: Driebergen-Rijsenburg
ISP: Vodafone Ziggo

You missed the second part. fido.vlist.eu has two A and two AAAA
records. I am multi homed, one connection with Ziggo via coax and
one connection to Delta via ftth.

Those details are not important for this report.

I say it exposes a significant shortcoming. Your application notices the case of more than one listed hostname but it misses the case of a hostname resolving to more than one IP.

But very important for my other projects. Please keep your multi homed setup running for several months. Thank you.

I'll try. No guarantee...

That must be confusing for those not not having read my Fidonews
articles about my DS-Lite emulation experiments. My binkp server
is located at my home in Driebergen NL. The German IPv4 adres
points to the V4 to V6 port mapper of feste-ip.net. It is a relic
of my DS-Lite emulation experiments.

The Germans would probably call it "Das Experiment".

BTW, I am not the only node in Fidonet that is dual homed...

Happy to hear that!

Happy enough to update your statistics accordingly?

BTW2 You missed 280/5006 becasue you dit not check for IPv6.
280/5006 is IPv6 only.

He is from "Heerhugowaard". I can't even pronounce that.

No need to pronounce it as long as your utility can write it.

"Heer" in Russian means "penis", BTW.

"Heer" means "Master" or "Lord. "Hugo" is a male name, like "Hugh" and "waard" in this context is arcahic for "estate". So it means "Master Hugh's Estate".

I could not help noticing the you are using the tactics of "the one who's name shall not be mentioned". You are changing the subject to divert from the fact that you do not support IPv6.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Hello, Michiel!

Saturday August 02 2025 12:36, you wrote to me:

It depends on who's running the investigation and doing the
questioning.

You run the application, I ask the question.

You see the same results as I do.

Those details are not important for this report.

I say it exposes a significant shortcoming. Your application notices
the case of more than one listed hostname but it misses the case of a hostname resolving to more than one IP.

But this node is still in NL, right? Only one node in Fidonet is located in multiple countries at the same time (because it's running on an SQL cluster) and this is not that node.

So as I said, it's not important because the result will be the same.

BTW, I am not the only node in Fidonet that is dual homed...

Happy to hear that!

Happy enough to update your statistics accordingly?

I was told in uni that a margin of error is acceptable as long as it's not critical for decision making.
This is exactly what's happening: only one node in FIdonet is truly multi-country based and it's still an experiment.

He is from "Heerhugowaard". I can't even pronounce that.

No need to pronounce it as long as your utility can write it.

She had a very hard job doing this and now she's very tired.

"Heer" in Russian means "penis", BTW.

"Heer" means "Master" or "Lord. "Hugo" is a male name, like "Hugh" and

As someone who was raised with egalitarian values, I don't like the idea of any "lords" or "masters". That's why the "penis" comparison was brought up here.

"waard" in this context is arcahic for "estate". So it means "Master Hugh's Estate".

So it's misleading name, rigth? "Master Hugh" is long dead and decomposed, that's not his estate. Probably it's good idea to rename it.
How about Groteplas?

Very easy to pronounce and shorter.

I could not help noticing the you are using the tactics of "the one
who's name shall not be mentioned". You are changing the subject to
divert from the fact that you do not support IPv6.

IPv6 is very inconvenient in a country with massive internet blocking. I am currently in Moscow and will be here for a relatively short period of time.
But my previous ISP in London also had zero IPv6 support.
I think IPv6 support in R50 will decrease, because many telcos are dropping support for it and he.net tunnels are already being blocked in some regions.

What is nore important for R50 is i2p support, Fido-over-DNS and Fido-over-ICMP support.

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello Dmitry,

On Saturday August 02 2025 14:14, you wrote to me:


[..]

I look forward to seeing your Fidonews article on this subject.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)