radikal.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
radikal.social was created by a group of activists to offer federated social media for the radical left in and around Denmark.

Administered by:

Server stats:

163
active users

#dns

6 posts6 participants1 post today

Online gambling operators are sponsoring charities?? If only :(

We've identified a malicious gambling affiliate whose specialty is to buy expired domain names which used to belong to charities or reputable organisations.

Once they own a domain, they host a website impersonating its previous owner, where they claim to "deeply appreciate the support from [their] sponsors", which surprise surprise, all turn out to be dubious online gambling companies.

Because the domain they are taking over is often abandoned or managed by non-technical people, its previous owner often doesn't notify anyone that they've lost control of their website, so it continues being referenced in genuine content, and it continues getting traffic from old links scattered throughout the internet.

teampiersma[.]org (screenshots below)
americankayak[.]org
getelevateapp[.]com
hotshotsarena[.]com
nehilp[.]org
questionner-le-numerique[.]org
sip-events[.]co[.]uk
studentlendinganalytics[.]com
thegallatincountynews[.]com

Comparison content:
2018: web.archive.org/web/2018011904
2025: web.archive.org/web/2025040109

Friendly reminder that you should be blocking all newly registered domains for your end users. Free lists like the NRD (github.com/xRuffKez/NRD) exist. Microsoft Defender for Endpoint also has a built in list you can enable via policy.

IMO everyone should do 365 days but even 30 or 90 will save you so much headache.
#DNS #ThreatIntel #FastFlux

A daily updated list of newly registered domains from the past 14 and 30 days for blocking, monitoring and analysis. - xRuffKez/NRD
GitHubGitHub - xRuffKez/NRD: A daily updated list of newly registered domains from the past 14 and 30 days for blocking, monitoring and analysis.A daily updated list of newly registered domains from the past 14 and 30 days for blocking, monitoring and analysis. - xRuffKez/NRD

🆕 blog! “How to prevent Payment Pointer fraud”

There's a new Web Standard in town! Meet WebMonetization - it aims to be a low effort way to help users passively pay website owners.

The pitch is simple. A website owner places a single new line in their HTML's <head> - something like this:

<link rel="monetization"…

👀 Read more: shkspr.mobi/blog/2025/03/how-t

#CyberSecurity #dns #HTML #standards #WebMonitization

Web Monetization The Web Monetization API allows websites to automatically and passively receive payments from Web Monetization-enabled visitors.
Terence Eden’s Blog · How to prevent Payment Pointer fraud
More from Terence Eden

I’ve been asked a few times over the course of the same amount of days, what would happen if the powers that be began deleting top-level domains (TLDs) from the DNS system, and whether there is something we (e.g. Asians, Africans, Europeans, Canadians, South Americans, Australians, etc.) could do about it.

A very theoretical scenario, DNS edition

jpmens.net/2025/03/27/theoreti

jpmens.netJan-Piet Mens :: A very theoretical scenario, DNS edition

Another round of “hey, your server is down!” drama from the "we need moar kubernetes!" crowd.

“I can’t reach your server, it must be down.”

I connect. Everything’s fine.

A few emails later, I ask to access the container. The dev says he can’t - doesn’t know how. He’s a nice guy, though, so he gives me the credentials.

I log in and find the issue: someone pushed a workload to production (cue Kubernetes! Moooaaarrr powaaaarrr! We have the cloud! Who needs sysadmins anymore?!) with DNS set to 192.168.1.1.

Of course, it fell to me to investigate, because the dev couldn’t even get a shell inside his container. And it's ok, as he's a dev - and just wants to be a dev.

Once I pointed it out, they rebuilt the container with the correct config and - TADA! - everything worked again.

Then he went to check other workloads (for other clients, not managed by me) that had been having issues for weeks... Same problem.

It was DNS.
But it wasn't DNS.

#IT#SysAdmin#DNS