Hostnames |
kumkangexpress.com www.kumkangexpress.com |
Domains | kumkangexpress.com |
Country | Korea, Republic of |
City | Ansan-si |
Organization | SK Broadband Co Ltd |
ISP | SK Broadband Co Ltd |
ASN | AS9318 |
-801460286 | 2024-09-13T18:22:08.37827880 / tcp
HTTP/1.1 302 Found Date: Fri, 13 Sep 2024 18:22:05 GMT Server: Apache Location: https://prok.org/ Content-Length: 201 Connection: close Content-Type: text/html; charset=iso-8859-1
-669598545 | 2024-09-20T12:10:23.430613443 / tcp
HTTP/1.1 200 OK Date: Fri, 20 Sep 2024 12:10:22 GMT Server: Apache X-Powered-By: PHP/5.2.17 Content-Length: 0 Connection: close Content-Type: text/html
Certificate: Data: Version: 3 (0x2) Serial Number: 08:65:d9:1c:09:84:f2:21:ea:19:a6:37 Signature Algorithm: sha256WithRSAEncryption Issuer: C=BE, O=GlobalSign nv-sa, CN=AlphaSSL CA - SHA256 - G2 Validity Not Before: Aug 27 06:23:18 2019 GMT Not After : Oct 5 06:46:00 2020 GMT Subject: C=KR, OU=Domain Control Validated, CN=www.kumkangexpress.com Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) Modulus: 00:a3:e5:04:38:7d:be:a2:de:c6:ea:b8:e2:8a:8b: 26:9c:be:3b:67:33:c1:93:e2:f1:3e:9f:7a:3c:be: ab:06:c3:61:2f:65:57:9a:d5:74:a3:f3:90:2e:e1: 21:4c:17:af:23:1d:40:1d:a8:12:57:2c:cf:51:00: ca:92:de:8f:bb:0d:90:1e:b8:45:c9:e5:1c:c9:3e: f8:53:a6:8b:cb:e1:39:d0:a6:6c:6f:ec:a3:25:11: 58:5c:e4:78:6d:4e:10:25:e5:3f:6c:5c:6f:99:7c: a3:1e:b8:b2:4e:27:fa:52:e7:ff:da:cd:9b:d5:aa: 0d:1b:32:2f:de:16:53:23:cf:7e:6d:65:f3:98:dd: 74:8e:b4:13:b3:f6:97:cb:06:5e:bb:9a:89:be:9d: 48:fa:bb:2c:13:06:e4:a4:1e:67:e5:51:1d:9e:7f: 1e:23:94:52:18:88:db:16:61:83:2e:83:96:0d:e2: 40:8f:51:5b:69:14:89:bd:47:af:33:9c:c2:bb:22: 8d:39:9b:56:34:1d:88:e2:c4:a3:07:b6:76:44:93: 04:12:14:92:91:cf:f0:d1:f1:7d:db:87:b2:4e:98: 3c:53:1e:61:45:9f:5e:93:db:46:53:1b:29:32:36: 9d:70:1a:f1:9a:62:10:1e:7a:85:83:0b:b1:04:e1: 9c:65 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Key Usage: critical Digital Signature, Key Encipherment Authority Information Access: CA Issuers - URI:http://secure2.alphassl.com/cacert/gsalphasha2g2r1.crt OCSP - URI:http://ocsp2.globalsign.com/gsalphasha2g2 X509v3 Certificate Policies: Policy: 1.3.6.1.4.1.4146.1.10.10 CPS: https://www.globalsign.com/repository/ Policy: 2.23.140.1.2.1 X509v3 Basic Constraints: CA:FALSE X509v3 CRL Distribution Points: Full Name: URI:http://crl2.alphassl.com/gs/gsalphasha2g2.crl X509v3 Subject Alternative Name: DNS:www.kumkangexpress.com, DNS:kumkangexpress.com X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Authority Key Identifier: F5:CD:D5:3C:08:50:F9:6A:4F:3A:B7:97:DA:56:83:E6:69:D2:68:F7 X509v3 Subject Key Identifier: 6F:97:EF:C0:C7:9E:E7:7E:BA:18:F7:F1:6D:2E:9F:E4:2A:D3:24:12 CT Precertificate SCTs: Signed Certificate Timestamp: Version : v1 (0x0) Log ID : A4:B9:09:90:B4:18:58:14:87:BB:13:A2:CC:67:70:0A: 3C:35:98:04:F9:1B:DF:B8:E3:77:CD:0E:C8:0D:DC:10 Timestamp : Aug 27 06:23:20.366 2019 GMT Extensions: none Signature : ecdsa-with-SHA256 30:45:02:21:00:DD:8E:6A:81:BA:E0:7D:36:DD:7E:7C: 2E:74:15:77:05:F6:6C:68:FC:3C:99:F7:AC:7D:C0:57: ED:2C:A0:86:F6:02:20:66:4F:86:08:66:E9:A4:B9:2F: FE:14:1C:72:D2:D4:F6:55:A8:33:86:1B:0F:81:B1:B3: 2F:74:49:FB:FC:19:A9 Signed Certificate Timestamp: Version : v1 (0x0) Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77: 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13 Timestamp : Aug 27 06:23:21.259 2019 GMT Extensions: none Signature : ecdsa-with-SHA256 30:44:02:20:18:42:E6:D3:6D:34:20:63:BD:D5:97:6D: 1D:54:F5:30:B5:24:A4:29:A2:EB:76:B5:CE:F6:3F:29: CC:15:43:F4:02:20:49:8A:9F:5B:5B:D0:E0:CA:54:71: 86:3F:F7:4F:DE:CB:61:57:E9:1B:0D:26:E0:75:5C:BC: D3:B2:44:BE:EF:D5 Signature Algorithm: sha256WithRSAEncryption Signature Value: 34:8f:b3:85:53:bc:b1:4b:75:d5:54:0c:79:e2:0d:75:e6:39: 6e:07:91:78:a2:63:a8:82:e6:bc:9b:de:4a:e1:f8:82:24:f6: f2:61:a4:cd:5e:a7:2d:32:aa:3f:41:5e:37:eb:91:cf:2a:b6: af:73:38:92:82:10:74:40:de:54:66:08:0a:5c:bb:32:79:35: 86:da:4d:d7:99:4d:0e:ba:5c:44:92:8d:e0:a4:e6:ae:e4:34: f7:06:c0:14:34:47:dc:6d:7c:e4:bc:81:31:9a:c2:25:a5:25: 07:3b:52:f6:df:07:af:4d:02:91:ca:fd:b2:e7:6b:e3:1b:3d: 92:de:80:3a:80:96:84:25:4e:bc:04:9e:9c:dd:dc:f7:ac:ef: d8:85:07:df:fb:29:a7:29:db:e7:85:b1:74:26:d1:a6:16:cf: b6:5b:2a:0a:f8:76:20:86:12:da:31:22:ec:fb:78:99:f8:30: 33:33:9c:a3:25:12:5c:93:27:c0:06:82:15:63:20:e1:79:e8: 52:63:e8:40:e8:a3:27:af:a4:95:05:68:f5:9a:e6:96:60:75: 42:98:2f:ea:c4:b3:12:7a:cb:7d:f4:b9:3e:7f:2b:75:b8:b7: ac:68:e8:ed:33:ed:7a:9e:3d:ed:7b:2f:ca:a8:be:09:f5:5a: 65:7d:2e:9d
-401605987 | 2024-09-18T15:42:33.4424018000 / tcp
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> Reason: You're speaking plain HTTP to an SSL-enabled server port.<br /> Instead use the HTTPS scheme to access this URL, please.<br /> <blockquote>Hint: <a href="https://www.ju-hyang.org/"><b>https://www.ju-hyang.org/</b></a></blockquote></p> </body></html>