Re:Tell HN: Ycombinator.com Blacklisted by Norton
by philip1209 on Monday October 31, 2016 @03:21PM
(#12840038)
Probably a Cloudflare IP got flagged then switched to serving YC traffic
[ Parent
| on HN ]
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by scrollaway on Monday October 31, 2016 @03:43PM
(#12840215)
We got that same issue on joust.hearthsim.net (serving an S3 static site), it's getting blocked in russia because some website used to be on the IP it's currently routed to, back in 2013 or some such.
Annoying. Any suggestions?
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by jgrahamc on Monday October 31, 2016 @04:20PM
(#12840578)
Did you talk to Cloudflare support about that?
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by scrollaway on Monday October 31, 2016 @04:22PM
(#12840600)
Yeah. They essentially advised us to open a new account. They also advised that we would be less likely to share an IP on a paid plan.
The website in question I don't think even exists anymore, so this is just a dead IP in russia.
I fucking hate censorship.
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by jgrahamc on Monday October 31, 2016 @04:23PM
(#12840606)
Drop me an email jgc@
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by jgrahamc on Monday October 31, 2016 @03:51PM
(#12840278)
ycombinator.com is not handled by Cloudflare; it appears to be on Amazon.
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by jonknee on Monday October 31, 2016 @04:59PM
(#12840874)
Hmm...
nslookup news.ycombinator.com
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
news.ycombinator.com canonical name = news.ycombinator.com.cdn.cloudflare.net.
Name: news.ycombinator.com.cdn.cloudflare.net
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by jgrahamc on Monday October 31, 2016 @05:41PM
(#12841190)
That's news.ycombinator.com not ycombinator.com. I was talking about the latter.
Re:Tell HN: Ycombinator.com Blacklisted by Norton
by philip1209 on Monday October 31, 2016 @05:45PM
(#12841216)
You're correct - at least one of the subdomains (hacker news) is on CF and I assumed the main site was on it too.
I don't know how Adobe flagging works - it's possible that detecting an issue on a subdomain would cause them to flag the apex. That being said, the same recycled-IP issue could apply to the Amazon load balancer / CDN.
[Edit] Looks like they do indeed classify by apex. So, news.ycombinator.com redirects to ycombinator.com on the Adobe database, e.g. https://safeweb.norton.com/report/show?url=news.ycombinator....