1
2

[–] IiIIy [S] 1 point 2 points (+3|-1) ago  (edited ago)

Domain isn't listed in the approved domains of the certs list.

Archive of imgTC.com = 403 (forbidden)

Maybe doing some maintenance? or hax..

[–] [deleted] 2 points 2 points (+4|-2) ago 

[Deleted]

0
3

[–] 8070631? 0 points 3 points (+3|-0) ago 

I'm getting the same warning.

0
6

[–] xyzzy 0 points 6 points (+6|-0) ago 

Yes, but it isn't THAT important. It's still safer than http links. And it's an image hoster after all, not some site you'd send sensitive information to.

[–] [deleted] ago 

[Deleted]

0
1

[–] Crow_T_robocop 0 points 1 point (+1|-0) ago 

Yes.

0
4

[–] discoball 0 points 4 points (+4|-0) ago 

I think their SSL cert expired.

0
2

[–] Improbablyanasshole 0 points 2 points (+2|-0) ago 

Likely what happened, atko did the same thing once probably not a big deal.

1
7

[–] IiIIy [S] 1 point 7 points (+8|-1) ago  (edited ago)

The cert would say it expired then.

Instead the cert being served doesn't even list their domain name, and is not expired / timed out.

0
1

[–] o0shad0o 0 points 1 point (+1|-0) ago  (edited ago)

Cert looks fine - you might be victims of a DNS spoof.

1
0

[–] IiIIy [S] 1 point 0 points (+1|-1) ago 

My apparent IP for imgtc.com: 50.7.103.59

What u got?

0
0

[–] o0shad0o ago 

Same.

0
0

[–] jmtullock2 ago 

I had to disable cloudflare while the ssl cert wasn't working. 50.7.103.59 is the ip address of my vps with fdcservers. the nameservers are normally ns1/2.imgtc.net, now they've returned to the cloudflare nameservers since its working again

0
0

[–] revofire ago 

What's worse is I get a 404 after I bypass.

0
1

[–] Warhymn 0 points 1 point (+1|-0) ago 

yes

1
1

[–] IiIIy [S] 1 point 1 point (+2|-1) ago 

can you ping imgtc.com see what IP you got?

0
1

[–] ToTheMoonAlice 0 points 1 point (+1|-0) ago  (edited ago)

Pinging imgtc.com [50.7.103.59] with 32 bytes of data:

Reply from 50.7.103.59: bytes=32 time=76ms TTL=40

Reply from 50.7.103.59: bytes=32 time=74ms TTL=40

Reply from 50.7.103.59: bytes=32 time=75ms TTL=40

Reply from 50.7.103.59: bytes=32 time=75ms TTL=40

0
3

[–] IiIIy [S] 0 points 3 points (+3|-0) ago 

Well, I seems like it's fine now for me.

Strange to have a hickup like that.

I could try and look up DNS record history see if the IP# changed and DNS was slow to propagate.. or not.. might be nothing.

I guess just keep an eye out for fuckery..

0
1

[–] Disappointed 0 points 1 point (+1|-0) ago 

Working for me.

1
1

[–] IiIIy [S] 1 point 1 point (+2|-1) ago  (edited ago)

This archive has 403 - Forbidden..
http://archive.is/HYRWm

..next hour:
http://archive.is/Sjuyi (fixxd)

Probably caught some hosting fuckery going on, so many layers now with colocation (cloudflare) DNS based load balancing, shared hosting..

..or, mebby caught hax slippin up, no telling without more research.. Meh. I'll just use one of the other IP farming image hosts for a bit. Wish imgjar had upload via URL.

load more comments ▼ (1 remaining)