this post was submitted on 11 Jan 2026
173 points (100.0% liked)

Selfhosted

54413 readers
847 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I generated 16 character (upper/lower) subdomain and set up a virtual host for it in Apache, and within an hour was seeing vulnerability scans.

How are folks digging this up? What's the strategy to avoid this?

I am serving it all with a single wildcard SSL cert, if that's relevant.

Thanks

Edit:

  • I am using a single wildcard cert, with no subdomains attached/embedded/however those work
  • I don’t have any subdomains registered with DNS.
  • I attempted dig axfr example.com @ns1.example.com returned zone transfer DENIED

Edit 2: I'm left wondering, is there an apache endpoint that returns all configured virtual hosts?

Edit 3: I'm going to go through this hardening guide and try against with a new random subdomain https://www.tecmint.com/apache-security-tips/

you are viewing a single comment's thread
view the rest of the comments
[–] 4am@lemmy.zip 31 points 18 hours ago* (last edited 18 hours ago) (2 children)

For anyone who needs to read it: At the end of the day this is obscurity, not security; however obscurity is a good secondary defense because it buys time.

I too would be interested to learn how this leaked

[–] zeca@lemmy.ml 1 points 4 hours ago (2 children)

Isnt security mostly achieved by heavy obscurity? A password secures because other people dont know what it is, it is obscured.

[–] pishadoot@sh.itjust.works 2 points 2 hours ago

They're not the same.

Hiding an unlocked treasure chest in the forest is obscurity. Sure, you might be the only one who knows it's there at first but eventually someone might come across it.

Having a vault at a bank branch is security - everyone knows there's a vault there, but you'll be damned if you're going to get into it when you're not authorized.

Good passwords, when implemented correctly, use hashing (one way encryption) to provide security. It's not obscured, people know you need a password to access the thing (in our example)

[–] bluehambrgr@lemmy.world 1 points 2 hours ago

In cryptography, there’s a difference between “secrets” (like passwords and encryption keys), and hiding / obscuring something (like steganography or changing your web server to run on a different port)

[–] chillpanzee@lemmy.ml 12 points 15 hours ago (2 children)

it's not even obscurity; it's logged publicly.

[–] sommerset@thelemmy.club 9 points 7 hours ago* (last edited 7 hours ago)

It's not. Wildcard DNS and wildcard cert. Domain is not logged publicly.

People that keep saying logged publicly simply don't understand setup and technology

[–] Keelhaul@sh.itjust.works 9 points 10 hours ago

How is it being logged publicly? Like OP said there is no specific subdomain registered in the DNS records (instead using a wildcard). Same for the SSL cert. Only things I can think of is the browser leaking the subdomains (through google or Microsoft) or the DNS queries themselves being logged and leaked. (Possibly by the ISP inspecting the traffic or logging and leaking on their own DNS servers?). I would hardly call either of those public.