Show preview thumbnail of the subdomain

[sir-kokabi]

Display preview thumbnails for all subdomains. Many of them display 404 errors, "This site can’t be reached" or other issues.

[wotschofsky]

Hi @sir-kokabi, thanks for raising this. What I hear is that you're regularly seeing false positives for whether a found subdomain is still active, correct?

Do you have examples of domains which have a lot of those false positives?

Are you thinking preview thumbnail in the sense of displaying a screenshot of said page?

[maaaathis]

I find it difficult to take screenshots of the page. If you use iframes or co, which are loaded clientside, then (at least) one request is sent from the client to the target page when the subdomains page is opened. But I can imagine that many users would not agree to simply send n requests from them directly to the pages.
The alternative here would be SSR, but I can well imagine that the hosting costs would increase exponentially if n previews are loaded when the subdomains page is called up.

[maaaathis]

Maybe a simple HTTP status code check would be sufficient instead?

[sir-kokabi]

Hi @sir-kokabi, thanks for raising this. What I hear is that you're regularly seeing false positives for whether a found subdomain is still active, correct?

Do you have examples of domains which have a lot of those false positives?

All these reports exist, but all of them returned the error:

This site can’t be reached

https://eggroll.ext.google.com/
https://alt1.aspmx.l.google.com/
https://alt1.gmail-smtp-in.l.google.com/
https://alt1.gmr-smtp-in.l.google.com/
https://alt2.gmail-smtp-in.l.google.com/
https://alt2.aspmx.l.google.com/
https://alt2.gmr-smtp-in.l.google.com/
https://alt3.aspmx.l.google.com/
https://alt3.gmail-smtp-in.l.google.com/
...

Are you thinking preview thumbnail in the sense of displaying a screenshot of said page?

Yes, as I mentioned in my use of digger.tools on #28 (comment), displaying a thumbnail of any page (whether error or no error) helps me locate what I'm searching for.

[sir-kokabi]

I find it difficult to take screenshots of the page. If you use iframes or co, which are loaded clientside, then (at least) one request is sent from the client to the target page when the subdomains page is opened. But I can imagine that many users would not agree to simply send n requests from them directly to the pages. The alternative here would be SSR, but I can well imagine that the hosting costs would increase exponentially if n previews are loaded when the subdomains page is called up.

I understand your point, but when I look at it from the perspective of a ruthless consumer who, at the highest level of perfection, envisions the best user experience for their intended goal, the presence of screenshots of the pages, despite their associated costs, seems excellent to me. I believe this is achievable, similar to how extensions like Speed Dial accomplish this. It could be made an optional setting for users who would like to enable it.

[wotschofsky]

I see: The domains you provided are part of Gmail and intended to receive incoming emails rather than for serving a webpage. While not technically "viewable" I'd still argue, that those are valid subdomains.

By this logic, would you say these here are valid subdomains?
https://static.wsky.dev/ (returns 404 at the root, but serves files at others paths)
https://notreallythere.digger.tools/ (has no Vercel deployment assigned)

Right now the subdomains list is rather compact. Where would you place these screenshots?

[sir-kokabi]

For the use case I mentioned, I am looking for any viewable domain that can be displayed as follows:

[wotschofsky]

Thanks for design sketch. As of now I don't believe this is a technically feasible feature without breaking the bank.
I'll keep the issue open nonetheless, in case something changes.

[ellieschieder]

All these reports exist, but all of them returned the error:

This site can’t be reached

https://eggroll.ext.google.com/ https://alt1.aspmx.l.google.com/ https://alt1.gmail-smtp-in.l.google.com/ https://alt1.gmr-smtp-in.l.google.com/ https://alt2.gmail-smtp-in.l.google.com/ https://alt2.aspmx.l.google.com/ https://alt2.gmr-smtp-in.l.google.com/ https://alt3.aspmx.l.google.com/ https://alt3.gmail-smtp-in.l.google.com/ ...

only because there is not Webserver running, it does not mean a site is not in use. The scope is to give active subdomains back and active in this case means more or less that it has a DNS response on that subdomain.