|
Lucky you, I'm straight up blocked. From multiple IPs even, chrome throws "ERR_CONNECTION_RESET" on 4G. And here's "curl" from my server * Hostname was NOT found in DNS cache
* Trying 192.104.54.190...
* Connected to apps.fcc.gov (192.104.54.190) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using DHE-RSA-AES256-GCM-SHA384
* Server certificate:
* subject: C=US; ST=District of Columbia; L=Washington; 1.3.6.1.4.1.311.60.2.1.3=US; O=Federal Communications Commission; businessCategory=Government Entity; serialNumber=06 19 1934; CN=apps.fcc.gov
* start date: 2015-09-13 15:38:08 GMT
* expire date: 2016-09-14 00:27:01 GMT
* subjectAltName: apps.fcc.gov matched
* issuer: C=US; O=Entrust, Inc.; OU=See www.entrust.net/legal-terms; OU=(c) 2014 Entrust, Inc. - for authorized use only; CN=Entrust Certification Authority - L1M
* SSL certificate verify ok.
> GET /oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&calledFromFrame=N&application_id=Ti%2FYleaJNSl%2BTR5mL5C0WQ%3D%3D&fcc_id=2ABCB-RPI32 HTTP/1.1
> User-Agent: curl/7.35.0
> Host: apps.fcc.gov
> Accept: */*
>
* SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
* Closing connection 0
curl: (56) SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
|