Hostnames |
mirairo.co.kr www.mirairo.co.kr |
Domains | mirairo.co.kr |
Country | Korea, Republic of |
City | Seongnam-si |
Organization | SK Broadband Co Ltd |
ISP | SK Broadband Co Ltd |
ASN | AS9318 |
920966318 | 2024-12-18T06:02:51.33883253 / tcp
UNKNOWN Resolver name: makedesign.kr
-1756192915 | 2024-12-22T19:27:04.43526853 / udp
Resolver name: makedesign.kr
-1468762852 | 2025-01-04T04:06:18.87236680 / tcp
HTTP/1.1 200 OK Date: Sat, 04 Jan 2025 04:06:14 GMT Server: Apache/2.2.3 (CentOS) X-Powered-By: PHP/5.2.17 Last-Modified: Tue 04 Sep 2012 07:00:05 GMT ETag: "Tue 04 Sep 2012 07:00:05" Content-Length: 64 Connection: close Content-Type: text/html; charset=EUC-KR
1806213784 | 2025-01-04T00:10:08.680152443 / tcp
HTTP/1.1 200 OK Date: Sat, 04 Jan 2025 00:10:06 GMT Server: Apache/2.2.3 (CentOS) X-Powered-By: PHP/5.2.17 Set-Cookie: LOG_HIT=Y; path=/ Content-Length: 383 Connection: close Content-Type: text/html; charset=EUC-KR
Certificate: Data: Version: 3 (0x2) Serial Number: cb:c8:65:f0:6d:55:b6:a6:30:05:56:e6:04:e1:45:7c Signature Algorithm: sha1WithRSAEncryption Issuer: C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=PositiveSSL CA 2 Validity Not Before: Sep 19 00:00:00 2012 GMT Not After : Sep 19 23:59:59 2013 GMT Subject: OU=Domain Control Validated, OU=PositiveSSL, CN=mirairo.co.kr Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) Modulus: 00:d9:36:7b:c1:3c:87:aa:62:3c:df:77:24:5f:59: 98:98:54:8c:ae:d5:68:d6:02:59:82:46:04:ac:74: 19:69:1a:b8:d3:18:1c:db:b4:f9:78:ba:ef:6d:ed: af:89:0b:d3:18:82:d8:0f:0e:23:77:b3:45:89:6d: 1a:a6:25:86:a4:78:dc:1c:5e:e2:38:4f:d9:b0:af: bd:be:b9:ae:1e:33:0b:f4:8a:30:56:b5:e2:ff:44: 54:0d:e8:fc:6b:34:7e:11:10:d8:b4:3f:da:26:46: 58:7b:ee:5f:76:36:54:3e:55:4e:90:d9:cd:e3:ca: 38:45:0e:48:75:f1:22:2e:66:a9:5b:9c:72:9c:41: 97:b0:d3:79:48:28:a2:76:10:cf:88:5f:eb:70:69: 6d:fd:dd:a8:8a:24:d8:31:a2:60:e3:46:40:ad:f8: 57:37:3a:89:25:38:eb:f4:97:f2:9b:d6:4a:09:2f: a4:12:79:89:4f:7b:5f:ed:a2:f2:0e:4a:18:84:a1: da:32:38:94:7a:31:9a:b1:bd:7f:ee:9b:70:cc:a5: 37:c7:26:d0:51:9f:8e:0c:e8:1e:7d:c3:10:45:0f: 0e:05:9d:49:d5:ed:2e:72:1f:89:e3:c6:d5:8e:22: 03:f0:98:6d:46:b3:01:1a:d1:8c:82:06:25:46:90: 2b:83 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Authority Key Identifier: 99:E4:40:5F:6B:14:5E:3E:05:D9:DD:D3:63:54:FC:62:B8:F7:00:AC X509v3 Subject Key Identifier: CD:7D:76:C2:42:2D:0D:D4:BB:73:DA:30:93:C9:F7:1C:62:28:FB:43 X509v3 Key Usage: critical Digital Signature, Key Encipherment X509v3 Basic Constraints: critical CA:FALSE X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7 CPS: http://www.positivessl.com/CPS X509v3 CRL Distribution Points: Full Name: URI:http://crl.comodoca.com/PositiveSSLCA2.crl Authority Information Access: CA Issuers - URI:http://crt.comodoca.com/PositiveSSLCA2.crt OCSP - URI:http://ocsp.comodoca.com X509v3 Subject Alternative Name: DNS:mirairo.co.kr, DNS:www.mirairo.co.kr Signature Algorithm: sha1WithRSAEncryption Signature Value: 0d:50:a0:6f:aa:8b:42:5e:2b:45:5b:e8:69:e6:f7:32:11:87: e5:fe:e8:77:a0:27:ac:5c:de:ad:3d:af:e6:28:af:62:1f:05: 97:2c:b0:eb:37:16:c2:b2:82:9e:6e:89:18:2c:24:33:15:c7: 2b:88:85:df:be:fe:c8:79:a3:41:82:0f:e3:2d:d8:a5:65:25: 7d:18:47:70:d4:78:6b:76:ef:07:5f:75:01:c9:f1:97:ef:88: d9:59:80:cc:a3:5e:16:dc:88:44:0a:cc:73:94:94:23:36:e1: dc:4a:a3:94:0b:3a:cc:24:aa:9b:6c:ac:4a:c1:b2:25:1e:e7: e2:b3:25:e4:50:eb:9a:80:c2:e2:d6:ab:df:f1:f4:bc:47:a5: ec:87:7c:3d:a4:cb:b2:1d:50:64:81:3f:86:b4:a3:8f:61:5c: d5:46:f9:84:02:14:89:4c:69:f9:7a:d2:f6:c1:e9:3c:40:65: ee:2f:6e:9a:b1:3a:de:f8:b5:17:51:cb:9e:4f:de:04:2a:43: 3c:b3:c3:29:31:df:bb:80:4a:eb:c9:8f:d7:87:05:d7:25:a8: 9f:38:8c:4e:19:27:ab:a1:d4:79:f4:fc:46:72:87:c1:a3:e0: 5d:50:1d:4b:8c:4e:9c:78:82:5c:d8:fa:c7:76:d9:4f:e2:f1: 57:48:72:d7
765379952 | 2025-01-03T07:24:25.936163448 / 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.ehaelimmok.com:448/"><b>https://www.ehaelimmok.com:448/</b></a></blockquote></p> <hr> <address>Apache/2.2.3 (CentOS) Server at www.ehaelimmok.com Port 448</address> </body></html>
450575606 | 2024-12-31T08:16:13.4797343306 / tcp
8\x00\x00\x00\n5.0.95-log\x00h/^\x05\\Aq8bbFv\x00,\xa2\x13\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00C+Inqi=52;qG\x00