Subj : ftsc.org problem
To   : Wilfred van Velzen
From : Alexey Vissarionov
Date : Tue Jan 24 2023 10:11 pm

Good ${greeting_time}, Wilfred!

24 Jan 2023 11:45:58, you wrote to deon:

 de>> I was going to refresh my memory from the standards, but it seems
 de>> that ftsc.org has not been renewed and now replaced by a common
 de>> parked page?
 WvV> Something seems wrong indeed. I get a blank page, but that is
 WvV> because my add blockers filter out all the sh*t. ;-) When I
 WvV> look at the source I indeed see a lot of javascript and some
 WvV> 'parking-lander' urls...

Something was changed today, 2023-01-24 08:03:25 UTC:

% whois ftsc.org | grep 2023
Updated Date: 2023-01-24T08:03:25Z

The A record was set to the address 34.160.209.102 (IPv4 only, duh), which belongs to some completely distrusted entity:

NetRange:       34.128.0.0 - 34.191.255.255
CIDR:           34.128.0.0/10
NetName:        GOOGL-2
NetHandle:      NET-34-128-0-0-1
Parent:         NET34 (NET-34-0-0-0-0)
NetType:        Direct Allocation
Organization:   Google LLC (GOOGL-2)

I don't know (and, honestly, don't care) who has access to edit the NS zone
contents, but this change looks unwise.

Anyway, I have a fresh backup :-)


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

.... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
--- /bin/vi
 * Origin: ::1 (2:5020/545)

.