Re:We spent $20 to achieve RCE and accidentally became the a...
by playingalong on Wednesday September 11, 2024 @12:06PM
(#41512689)
I think it's a sane practice to keep the marketing landing page on a separate domain than the product in case of SaaS.
[ Parent
| on HN ]
Re:We spent $20 to achieve RCE and accidentally became the a...
by declan_roberts on Wednesday September 11, 2024 @12:31PM
(#41512922)
Why? I always get frustrated when I end up in some parallel universe of a website (like support or marketing) and I can't easily click back to the main site.
Re:We spent $20 to achieve RCE and accidentally became the a...
by playingalong on Wednesday September 11, 2024 @05:24PM
(#41515464)
The non-technical reason is that these are usually owned by different teams in your org (after you mature beyond a 5-person startup).
The technical perspective is that things like wildcard subdomains (e.g. to support yourcustomername.example.com), or DNSSec if your compliance requires it, etc. cause an extra burden if done for these two use-cases at a time.
> can't easily click
Http pages don't have problems with having a link to example.net from within example.com. Or the opposite. Seems like an unrelated problem.
Re:We spent $20 to achieve RCE and accidentally became the a...
by thayne on Wednesday September 11, 2024 @09:16PM
(#41516723)
One potential reason is that marketing teams often want to do things that are higher risk than you may want to do on your main application domain. For example, hosting content (possibly involving a CNAME pointing to a domain outside your control) on a third party platform. Using a framework that may be less secure and hardened than your main application (for example WordPress or drupal with a ton of plugins) using third party Javascript for analytics, etc.
Re:We spent $20 to achieve RCE and accidentally became the a...
by stagalooo on Wednesday September 11, 2024 @12:31PM
(#41512929)
Could you elaborate on why? The companies I have worked for have pretty much all used domain.com for marketing and app.domain.com for the actual application. What's wrong with this approach?
Re:We spent $20 to achieve RCE and accidentally became the a...
by darkr on Wednesday September 11, 2024 @02:22PM
(#41513952)
If there’s any scope for a user to inject JavaScript, then potentially this gives a vector of attack against other internal things (e.g admin.domain.com, operations.domain.com etc)
Re:We spent $20 to achieve RCE and accidentally became the a...
by CountVonGuetzli on Wednesday September 11, 2024 @02:39PM
(#41514094)
Also, if for example the SaaS you’re running sends a lot of system emails that really shouldn’t end up in spam filters, you can’t afford to let things like marketing campaigns negatively influence your domain’s spam score.
Easier and safer to have separate domains.