Since a lot of people like to use it for archiving posts for reputation.
I had this in meta and some mod moved it, to off-topic. I think it's better here.
Just my opinion.
It's not much of a block but while browsing Ratimovs post
https://bitcointalksearch.org/topic/m.57979125 when clicking on the links it took me nowhere.
Thought it was odd and did some more checking. Turns out some ISPs or at least optimum are either deliberately blocking the site or have their DNS servers so screwed up you can't get to it.
Using 8.8.8.8 or 1.1.1.1 or 9.9.9.9 will get you to the site.
Using a PC I have access to on Fios it works.
Usain a PC I have access to on Spectrum it does not.
I don't know if this is a transient issue, or if it's deliberate, or even if Optimum / Spectrum even run their own DNS or subcontract it out so it might not even be them.
Just an FYI to people, who use the archive.*** service it may not work for some people.
It was working sometime last week, don't remember when I last clicked on one of those links.
-Dave
From cable:
HEADER:
opcode = QUERY, id = 29796, rcode = NOERROR
header flags: reply, want recursion, recursion avail.
questions = 1, answers = 1, auth. records = 0, additional = 0
QUESTIONS:
archive.today., type = XX, class = 1
ANSWERS:
-> archive.today.
type = CNAME, class = 1, ttl = 60, dlen = 19
alias = www.archive.today.
So I look up www.archive.today and get:
HEADER:
opcode = QUERY, id = 29841, rcode = NOERROR
header flags: reply, want recursion, recursion avail.
questions = 1, answers = 0, auth. records = 0, additional = 0
QUESTIONS:
www.archive.today., type = XX, class = 1
**complete**
Using 8.8.8.8 it works properly:
HEADER:
opcode = QUERY, id = 29891, rcode = NOERROR
header flags: reply, want recursion, recursion avail.
questions = 1, answers = 1, auth. records = 0, additional = 0
QUESTIONS:
archive.today., type = XX, class = 1
ANSWERS:
-> archive.today.
type = A, class = 1, ttl = 300, dlen = 4
IP address = 151.106.9.30
**complete**