Live data from Hacker News

Ask HN: Why buy domains and 301 redirect them to me?

news.ycombinator.com

31–40 of 135 posts

Re: Ask HN: Why buy domains and 301 redirect them to me?

#31
As others have mentioned this is likely one of a couple of scenarios, roughly ordered by my guess on likelihood:

- Attempting to use your legitimate content and services to improve the SEO rank of other domains (even unrelated ones). This can usually be checked by looking for a sitemap.xml, there will be pages not redirected to your site that contain pages of links.

- Closely following the above, the pages may not be links to other sites but might be hosting phishing pages for other services unrelated to yours. The redirect here acts as a bluff for casual inspection of the domain. You won't see page entries in a sitemap.xml file for these ones.

- Attempting to "age" a domain. Not many talk about this option, but new domains are a red flag to a lot of automated security processes. When purchasing a domain and giving it a history associated with a legitimate service they make the domain look less suspicious for future malicious use.

- Preparation for a targeted campaign. This is pretty unlikely, you need to be really worth a dedicated long term campaign effort specifically against you or your company. If you're doing controversial/novel research, are managing millions of dollars, performing a service a state actor would object to, or have high profile clientele then maybe you fall into this category. These are patient campaigns and want to make the domain "feel normal and official". They won't do anything public with the domain such as SEO tweaking or link spam, they'll use these domains only for specific targeted one-off low-noise attacks. They're relying on staff to see that the domain has been connected to your service for years and is likely just a domain someone in marketing purchased and forgot about. This is exceptionally rare.

Re: Ask HN: Why buy domains and 301 redirect them to me?

#32

I think you can check the HTTP_REFERER header and block the redirect using your back-end code, like PHP or Node or Python, not sure what tech stack you are using.

You can do the same with a load balancer or reverse proxy like nginx, and I’d generally prefer do to so at that layer.

Re: Ask HN: Why buy domains and 301 redirect them to me?

#33
Phishing. Regular visits to these domains will 301 redirect them to you, but there's at least one URL that will instead be handled by the scammers themselves.

They'll then send out an email campaign with a From: address in the counterfeit domain (which will have valid SPF/DKIM/whatever), a subject like "Example.com: You've been invited to join a project!", quickly-come-see-this-secret-stuff body copy, and a call-to-action button linked to that URL.

The page hosted on the URL will have your branding and everything, and collect a bunch of personal information and/or access credentials for the scammers.

Taking down this stuff is tedious, but you can try -- least you can do for now is display a prominent 'this is not an authorized example.com domain' warning for inbound visits from these redirects, create a public Knowledge Base-like article warning about this abuse as well (making very clear this has nothing to do with you), and block the domains involved on your inbound mail server.

Silver lining: apparently your SaaS is successful enough to be used as a lure for scammers. Congrats?

Re: Ask HN: Why buy domains and 301 redirect them to me?

#36
post #6
post #2

People do this for SEO purposes. They think that this increases the amount of backlinks to their site, thus increasing their rank in Google and other search engines. This is less true than it used to be, but people still do it.

Backlinks to which site? The fraudulent domains are only sending traffic to OP. My guess is that they want to either phish visitors, or they want to ask OP for affiliate revenue, like a digital version of the guys who wash your windshield or your shoes without asking first, and then ask for money. Or planning to threaten to divert organic traffic through the impersonation domains away from the canonical domain, if yo…

"Wash your winshield" lol are you South African?

Re: Ask HN: Why buy domains and 301 redirect them to me?

#37

I think you can check the HTTP_REFERER header and block the redirect using your back-end code, like PHP or Node or Python, not sure what tech stack you are using.

The right play might be to have a custom landing page or header / popup on your site indicating that they were referred by a fraudulent domain, and to please bookmark your proper domain / report if this was via an email link. The traffic might be good, just coming in through a bad actor.

Re: Ask HN: Why buy domains and 301 redirect them to me?

#38

As others have mentioned this is likely one of a couple of scenarios, roughly ordered by my guess on likelihood: - Attempting to use your legitimate content and services to improve the SEO rank of other domains (even unrelated ones). This can usually be checked by looking for a sitemap.xml, there will be pages not redirected to your site that contain pages of links. - Closely following the above, the pages may not be…

I think the first one is pretty likely.

OP, you can search for "site:getexample.com" which will list you any pages that have been indexed for that domain. They might have just redirected the homepage. Worth a shot.

Re: Ask HN: Why buy domains and 301 redirect them to me?

#39
I’ve seen one or two domains like that serving 301s to some IPs and their own website to others. This could be a 1000:1 ratio. Then they serve an absolutely ad-infested parking page-style website to those others. And that’s how they skim a little bit of revenue off your customers.

They may also represent you to real life businesses for invoice scams or credit.

Rare but possible scenarios worth considering.

Re: Ask HN: Why buy domains and 301 redirect them to me?

#40
post #26

Earlier quoted context omitted.

Couldn't the attacker evade that by sending Referrer-Policy: no-referrer with their redirect?

Good shout. Can always block based on origin header though (when under the assumption that it's a legit browser) since it's a forbidden header name. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Or...

I just tested on firefox and it doesn't send the "Origin" header when using referrerpolicy="no-referrer". It's also not present when navigating using the url bar directly.
Post reply on HN