Passive DNS on ns1.seizedservers.com is pretty interesting. It's where domains seized by the US government etc. go to die. Most of the domains here are extremely suspect (possibly CSAM-related), so proceed with caution. But it can be a good way to know when stuff actually gets seized by the government.
Still, it's not foolproof. I guess anyone can point their domain to these name servers.
Was recently chatting w/ a friend about this who remarked that putting a seizure warning on your site and pointing it to this name server would be a great way to run an exit scam for some crypto operation.
@briankrebs I'm not a DNS expert, but I'm kind of confused. If the owner of example.com sets their name server to that without seizedservers.com knowing, wouldn't seizedservers.com just give an error for the next lookup of A records for example.com?
@mwaters @briankrebs if the servers default site is the seized one, it works.
