Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #183906
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Newsgroups | alt.comp.software.thunderbird, alt.comp.os.windows-10, alt.comp.os.windows-11 |
| Subject | Re: ThunderMail is coming soon |
| Date | 2025-04-23 00:27 -0500 |
| Organization | Usenet Elder |
| Message-ID | <mal2pdx1v6gy.dlg@v.nguard.lh> (permalink) |
| References | (2 earlier) <1qtcu2gjgv16u$.dlg@v.nguard.lh> <m6nbgeF3dqsU1@mid.individual.net> <vu7ppj$bpdo$2@dont-email.me> <628uid68h3pn.dlg@v.nguard.lh> <vu89n2$pk6c$1@dont-email.me> |
Cross-posted to 3 groups.
Java Jive <java@evij.com.invalid> wrote: > VanguardLH wrote: > >> GDPR ruined DNS lookups by requiring redaction of registrants. Trying >> to get contact info on a domain registrant to alert them to a problem >> with their web site becomes much more difficult. Yeah, they want to >> provide a publicly accessible web site, but the registrant wants to >> hide. Thanks GDPR ... not! > > Can't say that I've noticed any such problem - I just use Whois - > so I suspect that this is just another example of someone from the > other side of the pond having an uninformed opinion against the EU > and its legislation. I meant domain lookups, not DNS lookups. When did you last do a WhoIs lookup on a domain? You get a privatized domain registration where the registrar pretends they are the registrant (IANA requires someone be identified as the registrant), or a registrant that is redacted, because the registrar follows GDPR rules. As for WhoIs, yes, that is what I'm talking about: look at a domain's registration which is required by IANA to provide contact information on /some/ registrant. To get around IANA's requirement, some registrars provided a private registration service at an extra fee. The registrant in the domain registration was the registrar instead of the actual registrant. Then came the GDPR where registrants could request their registrant data to get redacted, or the registrar did it en masse. So, when you lookup the domain registration, you got shit for registrant info. The primary impetus for hiding the registrant info was because there were spammers that would lookup up domain registrations to see which ones were about to expire, and offer their registration service. Registrants didn't want to get the spam, so they wanted to hide their identification in the domain registration records. With privatized registration, the registrar was identified as the registrant. The registrar handled the "renew your domain with us" spam. The whole point of privatized registration was to hide the real registrant. The solution was extremely simple: use an e-mail address specifying and only for domain registration with your registrar. Create an e-mail account for just domain registration notifications, and add a filter that accepted e-mails only from your registrar, so all other messages get immediately discard on delivery. You could identify yourself as the registrant, and even give postal addresses (since spammers don't pay for a stamp to send spam). Then later came the GDPR where registrants could hide without having to pay extra for privatized registration. The registrant info got redacted to point at a registrar, or one of their services, like e-mail addresses that pointed back to the registrar. https://www.whois.com/whois/domaintools.com is registered with TuCows, and says the registrant is: https://tieredaccess.com/contact/eceac3b1-4ae2-4ab0-a2d8-f7647c12c66b but: https://www.whois.com/whois/tieredaccess.com shows that domain is TuCows, the registrar. The domaintools.com registration hides the actual registrant, and the purported registrant is the registrar whose domain lookup is not redacted for registrant info. Sorry to those who suggest a web site should provide contact information. Yeah, like that really works ... NOT! Rare few sites provide contact information. Instead they may provide a web form to contact them. Or worse is they push some AI chat bot at you that is of no help at all, and worthless to report problems to the website. Oh yes, send an e-mail to webmaster@<domain> or postmaster@<domain>. Most often those are bit buckets to automatically discard those messages. Those that suggest this method haven't tried it. The success rate is about the same as firing a .22 rifle while blindfolded at a pinata from a quarter mile away. It's not just small fry that get to hide it's their web site. Huge corporations do it, too. So, why continue with bogus domain registration records that do not identify the registrant? None of the other remaining information is of any value. All you're left with nowadays is to see when a domain got registered, when last updated, and when it expires. The whole point of WhoIS was neutered by privatized domain registrations, and then by the GDPR. So, just get rid of all domain lookups, and leave everyone in the dark who is operating a web site since that is effectively what WhoIs has become: nearly worthless.
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
ThunderMail is coming soon James <invalid@invalid.invalid> - 2025-04-20 19:15 +0000
Re: ThunderMail is coming soon Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-20 20:35 +0100
Re: ThunderMail is coming soon "Carlos E.R." <robin_listas@es.invalid> - 2025-04-20 21:50 +0200
Re: ThunderMail is coming soon Chris <ithinkiam@gmail.com> - 2025-04-21 16:13 +0000
Re: ThunderMail is coming soon kyonshi <gmkeros@gmail.com> - 2025-04-20 21:42 +0200
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-20 15:46 -0500
Re: ThunderMail is coming soon Andy Burns <usenet@andyburns.uk> - 2025-04-21 08:52 +0100
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-21 17:36 -0500
Re: ThunderMail is coming soon Paul <nospam@needed.invalid> - 2025-04-22 05:58 -0400
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-22 07:43 -0500
Re: ThunderMail is coming soon Daniel70 <daniel47@eternal-september.org> - 2025-04-22 23:42 +1000
Re: ThunderMail is coming soon Dave Royal <dave@dave123royal.com> - 2025-04-20 21:12 +0100
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-20 15:49 -0500
Re: ThunderMail is coming soon "s|b" <me@privacy.invalid> - 2025-04-21 18:53 +0200
Re: ThunderMail is coming soon Daniel70 <daniel47@eternal-september.org> - 2025-04-22 20:07 +1000
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-22 07:49 -0500
Re: ThunderMail is coming soon Chris <ithinkiam@gmail.com> - 2025-04-22 13:58 +0000
Re: ThunderMail is coming soon Frank Slootweg <this@ddress.is.invalid> - 2025-04-22 15:32 +0000
Re: ThunderMail is coming soon David <BD@invalid.now> - 2025-05-03 14:50 +0100
Re: ThunderMail is coming soon Paul <nospam@needed.invalid> - 2025-05-03 14:39 -0400
Re: ThunderMail is coming soon Mark Lloyd <not.email@all.invalid> - 2025-05-03 19:14 +0000
Re: ThunderMail is coming soon "Carlos E.R." <robin_listas@es.invalid> - 2025-05-03 23:53 +0200
Re: ThunderMail is coming soon Chris <ithinkiam@gmail.com> - 2025-05-04 13:31 +0000
Re: ThunderMail is coming soon Frank Slootweg <this@ddress.is.invalid> - 2025-05-04 13:59 +0000
Re: ThunderMail is coming soon Java Jive <java@evij.com.invalid> - 2025-04-22 15:39 +0100
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-23 00:27 -0500
Re: ThunderMail is coming soon Java Jive <java@evij.com.invalid> - 2025-04-23 11:31 +0100
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-23 06:14 -0500
Re: ThunderMail is coming soon Java Jive <java@evij.com.invalid> - 2025-04-23 12:36 +0100
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-23 06:50 -0500
Re: ThunderMail is coming soon Chris <ithinkiam@gmail.com> - 2025-04-23 15:54 +0000
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-24 05:00 -0500
Re: ThunderMail is coming soon Philip Herlihy <nothing@invalid.com> - 2025-04-24 12:19 +0100
Re: ThunderMail is coming soon "R.Wieser" <address@is.invalid> - 2025-04-24 14:33 +0200
Re: ThunderMail is coming soon Philip Herlihy <nothing@invalid.com> - 2025-04-25 12:54 +0100
Re: ThunderMail is coming soon "R.Wieser" <address@is.invalid> - 2025-04-25 18:03 +0200
Re: ThunderMail is coming soon Philip Herlihy <nothing@invalid.com> - 2025-04-29 16:48 +0100
Re: ThunderMail is coming soon Chris <ithinkiam@gmail.com> - 2025-04-24 15:27 +0000
Re: ThunderMail is coming soon "R.Wieser" <address@is.invalid> - 2025-04-24 18:37 +0200
Re: ThunderMail is coming soon Trump Lost The Tariff War <Trump@US.Gov> - 2025-04-24 17:30 +0000
Re: ThunderMail is coming soon "R.Wieser" <address@is.invalid> - 2025-04-24 21:48 +0200
Re: ThunderMail is coming soon "R.Wieser" <address@is.invalid> - 2025-04-23 09:45 +0200
Re: ThunderMail is coming soon "R.Wieser" <address@is.invalid> - 2025-04-23 09:45 +0200
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-20 15:47 -0500
Re: ThunderMail is coming soon "John C." <r9jmg0@yahoo.com> - 2025-04-21 03:45 -0700
Re: ThunderMail is coming soon Char Jackson <none@none.invalid> - 2025-04-22 21:14 -0500
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-23 00:54 -0500
Re: ThunderMail is coming soon Philip Herlihy <nothing@invalid.com> - 2025-04-21 13:00 +0100
Re: ThunderMail is coming soon Roberto <dash@dominus.net> - 2025-04-21 19:26 +0200
Re: ThunderMail is coming soon Robert <monstoor@spammedia.com> - 2025-04-23 00:15 +0100
Re: ThunderMail is coming soon NZ Rules OK <invalid@invalid.invalid> - 2025-04-23 00:49 +0100
Re: ThunderMail is coming soon Nobody <jock@soccer.com> - 2025-04-22 18:36 -0700
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-04-24 05:07 -0500
Re: ThunderMail is coming soon Robert <monstoor@spammedia.com> - 2025-04-25 00:26 +0100
Re: ThunderMail is coming soon "John C." <r9jmg0@yahoo.com> - 2025-04-25 05:44 -0700
Re: ThunderMail is coming soon VanguardLH <V@nguard.LH> - 2025-05-16 06:26 -0500
Re: ThunderMail is coming soon "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-05-21 02:18 +0800
Re: ThunderMail is coming soon Retirednoguilt <HapilyRetired@fakeaddress.com> - 2025-05-21 10:50 -0400
csiph-web