StuntPope
Trezor breach victims now getting malicious QR codes by postal mail
These ones are handy:
1. What is my public IP
2. What is my DNS resolver (handy)
3. Is this a homoglyph (have your openclaw check this before blindly following a link)
4. SPF Flattener
5. DNS Twister
More to come.
Show HN: DNSskills.md – agentic skills for certain DNS utilities
Bought an expired domain. Then I inherited their AWS Root account
Show HN: Tunnel.to – dead simple localhost reverse tunnels
GPG-encrypted email forwarding is back, and the mxcrypt relay is now open source
Internet Content Regulation Is Coming to Canada
Age verification now required for DNS resolution
Repricing Sovereignty: Personal Freedom in the Age of Mass Compliance
Can x402 save the Open Source Software movement?
No, Your chatbot can't be hacked via DNS (at least not on its own)
Grappling with the Existential Panic over AI
Is ChatGPT Intentionally Driving You into Psychosis?
Krebs need to ditch the TDS.
His "Red Herring DNS flaw" garbage was when I realized that 90% of what he spits out is Gell-Mann amnesia.
Canada's "Strong Borders Act" (Bill C-2) Contains Four Surveillance Provisions
EasyDNS First to Use AI to Answer All DNS Queries
"It's the denominator, stupid" (Groking Bitcoin's inexorable rise)
If you want to get with a registrar who is actually clueful about takedowns, we can help you out.
Crontab.ninja: natural language in, cron expression out
As I posted on Krebs' article:
This is neither news nor new. There have been prior panics around this “water is wet” type issue going back at least a decade.
(Search up “Floating Domains – Taking Over 20K DigitalOcean Domains via a Lax Domain Import System” – and others).
I also wrote about this on CircleID from the DNS operator’s perspective (“Nameserver Operators Need the Ability to “Disavow” Domains”) – after this same issue was used to DDoS attack another DNS provider by delegating a domain to their DNS servers without having setup an account there, and then doing a DNS reflection attack on that domain. That was over ten years ago.
The fact that people can delegate their own domains to somebody else’s nameservers without ever properly setting up a zone on those nameservers, or ever keeping track of where THEIR OWN DOMAINS point is 100% the responsibility of the domain owner – and to varying degrees a function of their REGISTRAR – who is the only entity that has any control over it.
It’s a weird flex for corporate registrars who purport to be “high touch” and exclusive, to simply shrug their shoulders and turn a blind eye to their own clients’ obviously broken and vulnerable nameserver delegations.
For our part this is specifically one of things we actively monitor and alert our clients about.