Check website https://t1-tor-2.check-host.eu
| Location | Result | Time | Code | IP Address |
|---|---|---|---|---|
|
Albania, Tirana
|
Network error [EPROTO]: write EPROTO 301B3D7F957F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.25 s | 0 |
85.195.253.142
|
|
Australia, Sydney
|
Network error [EPROTO]: write EPROTO 308BEDF87A7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.54 s | 0 |
85.195.253.142
|
|
Bosnia and Herzegovina, Novi Travnik
|
Network error [EPROTO]: write EPROTO 309B5FF4E67F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.07 s | 0 |
85.195.253.142
|
|
Bulgaria, Sofia
|
Network error [EPROTO]: write EPROTO 303B1767EB7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.07 s | 0 |
85.195.253.142
|
|
Canada, Montreal
|
Network error [EPROTO]: write EPROTO 303BE930677F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.20 s | 0 |
85.195.253.142
|
|
Switzerland, Bern
|
Network error [EPROTO]: write EPROTO 30DB89BACE7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.02 s | 0 |
85.195.253.142
|
|
Chile, Santiago
|
Network error [EPROTO]: write EPROTO 303BCF3BF77F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.42 s | 0 |
85.195.253.142
|
|
China, Hohhot
|
Network error [ERR_CANCELED]: Timeout (15000ms) | 15.00 s | 0 |
85.195.253.142
|
|
Germany, Nuernberg
|
Network error [EPROTO]: write EPROTO 302B6D61AE7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.03 s | 0 |
85.195.253.142
|
|
Germany, Frankfurt am Main
|
Network error [EPROTO]: write EPROTO 30ABA938DA7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.05 s | 0 |
85.195.253.142
|
|
Germany, Frankfurt am Main
|
Network error [EPROTO]: write EPROTO 30DB6D612E7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.02 s | 0 |
85.195.253.142
|
|
Germany, Limburg
|
Network error [EPROTO]: write EPROTO 30EB88832A7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.03 s | 0 |
85.195.253.142
|
|
Germany, Frankfurt am Main
|
Network error [EPROTO]: write EPROTO 30AB2984FB7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.05 s | 0 |
85.195.253.142
|
|
Denmark, Glostrup Municipality
|
Network error [EPROTO]: write EPROTO 30AB3BE09C7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.14 s | 0 |
85.195.253.142
|
|
Spain, Bilbao
|
Network error [EPROTO]: write EPROTO 303B9D1EFC7E0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.13 s | 0 |
85.195.253.142
|
|
Finland, Helsinki
|
Network error [EPROTO]: write EPROTO 307BF8729F7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.12 s | 0 |
85.195.253.142
|
|
Finland, Helsinki
|
Network error [EPROTO]: write EPROTO 30BBB621DD7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.08 s | 0 |
85.195.253.142
|
|
France, Gravelines
|
Network error [EPROTO]: write EPROTO 302B8A87D27F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.04 s | 0 |
85.195.253.142
|
|
France, Paris
|
Network error [EPROTO]: write EPROTO 30CBB258057F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.12 s | 0 |
85.195.253.142
|
|
United Kingdom, London
|
Network error [EPROTO]: write EPROTO 305B865B2D7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.05 s | 0 |
85.195.253.142
|
|
Georgia, Tbilisi
|
Network error [ERR_CANCELED]: Timeout (15000ms) | 15.00 s | 0 |
t1-tor-2.check-host.eu
|
|
Hong Kong, Hong Kong
|
Network error [EPROTO]: write EPROTO 30ABA7ED4A7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.04 s | 0 |
85.195.253.142
|
|
Croatia, Zagreb
|
Network error [EPROTO]: write EPROTO 30DB7D64387F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.11 s | 0 |
85.195.253.142
|
|
Hungary, Budapest
|
Network error [EPROTO]: write EPROTO 307BFD9BD07F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.19 s | 0 |
85.195.253.142
|
|
Indonesia, Jakarta
|
Network error [EPROTO]: write EPROTO 30CB94E9FA7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.50 s | 0 |
85.195.253.142
|
|
Israel, Petach Tikwa
|
Network error [EPROTO]: write EPROTO 30BB53A86B7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.20 s | 0 |
85.195.253.142
|
|
Israel, Netanja
|
Network error [EPROTO]: write EPROTO 304BA85FA47F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.18 s | 0 |
85.195.253.142
|
|
India, New Delhi
|
Network error [EPROTO]: write EPROTO 300BDF86657F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.54 s | 0 |
85.195.253.142
|
|
Iceland, Reykjavik (Miðborg)
|
Network error [EPROTO]: write EPROTO 308BB626A57F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.12 s | 0 |
85.195.253.142
|
|
Italy, Como
|
Network error [EPROTO]: write EPROTO 307B8490687F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.04 s | 0 |
85.195.253.142
|
|
Lithuania, Pilaite
|
Network error [EPROTO]: write EPROTO 308B76B8C37F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.19 s | 0 |
85.195.253.142
|
|
Latvia, Riga
|
Network error [EPROTO]: write EPROTO 309B40B4057F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.26 s | 0 |
85.195.253.142
|
|
Moldova, Chisinau
|
Network error [EPROTO]: write EPROTO 301B2FCE2F7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.24 s | 0 |
85.195.253.142
|
|
Netherlands, Amsterdam
|
Network error [EPROTO]: write EPROTO 309B5315317F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.03 s | 0 |
85.195.253.142
|
|
Netherlands, Amsterdam
|
Network error [EPROTO]: write EPROTO 30EB627FC27F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.04 s | 0 |
85.195.253.142
|
|
Netherlands, Amsterdam
|
Network error [EPROTO]: write EPROTO 302B8005A87F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.03 s | 0 |
85.195.253.142
|
|
Netherlands, Amsterdam
|
Network error [EPROTO]: write EPROTO 300BCA1DE47F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.03 s | 0 |
85.195.253.142
|
|
Norway, Oslo
|
Network error [EPROTO]: write EPROTO 305BD1D0D97F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.06 s | 0 |
85.195.253.142
|
|
Poland, Warsaw
|
Network error [EPROTO]: write EPROTO 305B92FE507F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.10 s | 0 |
85.195.253.142
|
|
Romania, Bacău
|
Network error [EPROTO]: write EPROTO 308BBE7E5E7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.08 s | 0 |
85.195.253.142
|
|
Romania, Bucharest
|
Network error [EPROTO]: write EPROTO 30BB741E697F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.07 s | 0 |
85.195.253.142
|
|
Serbia, Belgrade
|
Network error [EPROTO]: write EPROTO 30EB79889C7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.23 s | 0 |
85.195.253.142
|
|
Russia, Moscow
|
Network error [EPROTO]: write EPROTO 302BFAF7BA7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.10 s | 0 |
85.195.253.142
|
|
Saudi Arabia, Riyadh
|
Network error [EPROTO]: write EPROTO 301B7E12757F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.38 s | 0 |
85.195.253.142
|
|
Singapore, Singapore
|
Network error [EPROTO]: write EPROTO 307BC2DEA27F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.35 s | 0 |
85.195.253.142
|
|
Tor, Onion
|
Network error [EPROTO]: write EPROTO 302BEB21AA7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.26 s | 0 |
t1-tor-2.check-host.eu
|
|
Tor, Onion
|
Network error [EPROTO]: write EPROTO 302B8A036A7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.44 s | 0 |
t1-tor-2.check-host.eu
|
|
Tor, Onion
|
Network error [EPROTO]: write EPROTO 304B03CEB77F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.20 s | 0 |
t1-tor-2.check-host.eu
|
|
Turkey, Istanbul
|
Network error [EPROTO]: write EPROTO 308B8971867F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.09 s | 0 |
85.195.253.142
|
|
Taiwan, Taipei
|
Network error [EPROTO]: write EPROTO 18EB6A77DB760000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.51 s | 0 |
85.195.253.142
|
|
United States, Miami
|
Network error [EPROTO]: write EPROTO 307B80DB577F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.24 s | 0 |
85.195.253.142
|
|
United States, Dallas
|
Network error [EPROTO]: write EPROTO 303B578BEA7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.26 s | 0 |
85.195.253.142
|
|
United States, Kansas City
|
Network error [EPROTO]: write EPROTO 304B35FC5E7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.28 s | 0 |
85.195.253.142
|
|
United States, Dallas
|
Network error [EPROTO]: write EPROTO 30CB8FB0C47F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.26 s | 0 |
85.195.253.142
|
|
South Africa, Johannesburg
|
Network error [EPROTO]: write EPROTO 305B63E26E7F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:918:SSL alert number 112 | 0.34 s | 0 |
85.195.253.142
|
ISP
Globalhost
Datacenter
Globalhost
ASNAS200698
Sponsored by Globalhost d.o.o. - Web Hosting Solutions
ISP
Marc Fischer - Packets-Decreaser
Datacenter
Equinix FR7
ASNAS214243
Sponsored by Packets-Decreaser Hosting