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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
173
How are people discovering random subdomains on my server? (lemmy.blahaj.zone)
submitted 20 hours ago* (last edited 19 hours ago) by BonkTheAnnoyed@lemmy.blahaj.zone to c/selfhosted@lemmy.world
74 comments fedilink hide all child comments
 

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
[–] androidul@lemmy.world 80 points 19 hours ago* (last edited 18 hours ago) (3 children)

if you use Let’s Encrypt (ACME protocol) AFAIK you can find all domains registered in a directory that even has a search, no matter if it’s wildcard or not.

It was something like this https://crt.sh/ but can’t find the site exactly anymore

LE: you can also find some here https://search.censys.io/

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

Holy shit... I thought it was DNS resolver selling these data

[–] Shimitar@downonthestreet.eu 15 points 13 hours ago (1 children)

This.

That's why temping obscurity for security is not a good idea. Doesn't take much to be "safe", at least reasonably safe. But that not much its good practice to be done :)

[–] sommerset@thelemmy.club 2 points 6 hours ago (1 children)

No. Not this.

Op is doing hidden subdomain pattern. Wildcard dns and wildcard ssl.

This way subdomain acts as a password and application essentially inaccessible for bot crawls.

Works very well

[–] atzanteol@sh.itjust.works 8 points 6 hours ago (1 children)

Apparently it doesn't.

[–] sommerset@thelemmy.club 1 points 5 hours ago

minimal setup is still required 🤷

[–] i_stole_ur_taco@lemmy.ca 39 points 18 hours ago (1 children)

Holy shit, this has every cert I’ve ever generated or renewed since 2015.

[–] vf2000@lemmy.zip 38 points 17 hours ago* (last edited 17 hours ago)

Certificate Transparency makes public all issued certificates in the form of a distributed ledger, giving website owners and auditors the ability to detect and expose inappropriately issued certificates.

https://en.wikipedia.org/wiki/Certificate_Transparency