SSL完整性监控API提供强大的工具来分析和验证网站的SSL证书,保护传输过程中的敏感数据。该API检查证书的有效性、过期时间、加密协议和颁发机构,确保用户的连接安全。通过基于JSON的响应,它无缝集成到您的工作流程中,自动化证书审计,检测漏洞,并保持与不断变化的安全标准的合规性,抵御网络威胁
要使用此端点,您需要在请求中提交网站URL。API验证SSL证书并返回有关其有效性、过期时间和加密设置的详细信息
验证Ssl - 端点功能
| 对象 | 描述 |
|---|---|
domain |
[必需] |
{"isvalidCertificate":true,"canBeSelfSigned":false,"isWildCard":true,"isExpired":false,"message":"Valid Certificate","expiry":"2025-07-27","daysLeft":242,"lifespanInDays":335,"issuer":"DigiCert Global CA G2 DigiCert Inc","certDetails":{"name":"\/CN=*.peg.a2z.com","subject":{"CN":"*.peg.a2z.com"},"hash":"3cae1f61","issuer":{"C":"US","O":"DigiCert Inc","CN":"DigiCert Global CA G2"},"version":2,"serialNumber":"4891915750396980015937368629838977478","serialNumberHex":"03AE261164DB2D8F280B8821F48199C6","validFrom":"240826000000Z","validTo":"250727235959Z","validFrom_time_t":1724630400,"validTo_time_t":1753660799,"signatureTypeSN":"RSA-SHA256","signatureTypeLN":"sha256WithRSAEncryption","signatureTypeNID":668,"purposes":{"1":[true,false,"sslclient"],"2":[true,false,"sslserver"],"3":[true,false,"nssslserver"],"4":[false,false,"smimesign"],"5":[false,false,"smimeencrypt"],"6":[false,false,"crlsign"],"7":[true,true,"any"],"8":[true,false,"ocsphelper"],"9":[false,false,"timestampsign"]},"extensions":{"authorityKeyIdentifier":"24:6E:2B:2D:D0:6A:92:51:51:25:69:01:AA:9A:47:A6:89:E7:40:20","subjectKeyIdentifier":"DB:DB:B1:DA:10:24:B4:C7:1A:82:93:C7:01:23:88:CF:0D:C3:E5:0D","subjectAltName":"DNS:amazon.co.uk, DNS:uedata.amazon.co.uk, DNS:www.amazon.co.uk, DNS:origin-www.amazon.co.uk, DNS:*.peg.a2z.com, DNS:amazon.com, DNS:amzn.com, DNS:uedata.amazon.com, DNS:us.amazon.com, DNS:www.amazon.com, DNS:www.amzn.com, DNS:corporate.amazon.com, DNS:buybox.amazon.com, DNS:iphone.amazon.com, DNS:yp.amazon.com, DNS:home.amazon.com, DNS:origin-www.amazon.com, DNS:origin2-www.amazon.com, DNS:buckeye-retail-website.amazon.com, DNS:huddles.amazon.com, DNS:amazon.de, DNS:www.amazon.de, DNS:origin-www.amazon.de, DNS:amazon.co.jp, DNS:amazon.jp, DNS:www.amazon.jp, DNS:www.amazon.co.jp, DNS:origin-www.amazon.co.jp, DNS:*.aa.peg.a2z.com, DNS:*.ab.peg.a2z.com, DNS:*.ac.peg.a2z.com, DNS:origin-www.amazon.com.au, DNS:www.amazon.com.au, DNS:*.bz.peg.a2z.com, DNS:amazon.com.au, DNS:origin2-www.amazon.co.jp, DNS:edgeflow.aero.4d5ad1d2b-frontier.amazon.co.jp, DNS:edgeflow.aero.04f01a85e-frontier.amazon.com.au, DNS:edgeflow.aero.47cf2c8c9-frontier.amazon.com, DNS:edgeflow.aero.abe2c2f23-frontier.amazon.de, DNS:edgeflow.aero.bfbdc3ca1-frontier.amazon.co.uk, DNS:edgeflow-dp.aero.4d5ad1d2b-frontier.amazon.co.jp, DNS:edgeflow-dp.aero.04f01a85e-frontier.amazon.com.au, DNS:edgeflow-dp.aero.47cf2c8c9-frontier.amazon.com, DNS:edgeflow-dp.aero.bfbdc3ca1-frontier.amazon.co.uk, DNS:edgeflow-dp.aero.abe2c2f23-frontier.amazon.de","certificatePolicies":"Policy: 2.23.140.1.2.1\n CPS: http:\/\/www.digicert.com\/CPS","keyUsage":"Digital Signature, Key Encipherment","extendedKeyUsage":"TLS Web Server Authentication, TLS Web Client Authentication","crlDistributionPoints":"Full Name:\n URI:http:\/\/crl3.digicert.com\/DigiCertGlobalCAG2.crl\nFull Name:\n URI:http:\/\/crl4.digicert.com\/DigiCertGlobalCAG2.crl","authorityInfoAccess":"OCSP - URI:http:\/\/ocsp.digicert.com\nCA Issuers - URI:http:\/\/cacerts.digicert.com\/DigiCertGlobalCAG2.crt","basicConstraints":"CA:FALSE","ct_precert_scts":"Signed Certificate Timestamp:\n Version : v1 (0x0)\n Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:\n 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A\n Timestamp : Aug 26 17:46:50.162 2024 GMT\n Extensions: none\n Signature : ecdsa-with-SHA256\n 30:46:02:21:00:86:83:64:1B:5C:A8:AC:61:D7:81:C6:\n A0:C7:53:37:11:D9:FD:27:AB:29:92:C1:3F:2F:A5:59:\n 40:2B:3F:1C:5C:02:21:00:E0:0A:6D:A2:F2:C4:98:78:\n 93:2A:C5:CF:F5:98:DA:E3:4B:56:89:1F:2D:63:B9:A2:\n 39:96:B8:EF:EB:CA:30:8D\nSigned Certificate Timestamp:\n Version : v1 (0x0)\n Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:\n D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50\n Timestamp : Aug 26 17:46:50.178 2024 GMT\n Extensions: none\n Signature : ecdsa-with-SHA256\n 30:45:02:20:65:F5:3D:C3:2A:8F:C6:C0:BC:7F:BF:37:\n 5C:15:A9:B9:FA:F9:EE:65:C2:DC:18:DC:5C:7F:73:59:\n 3B:79:A0:5A:02:21:00:EE:45:E3:C5:29:68:6A:23:EE:\n FF:8E:D9:F3:86:F4:8F:34:68:FF:6E:D8:8F:FA:6E:70:\n D5:17:6F:FB:CC:FD:4C\nSigned Certificate Timestamp:\n Version : v1 (0x0)\n Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:\n 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0\n Timestamp : Aug 26 17:46:50.170 2024 GMT\n Extensions: none\n Signature : ecdsa-with-SHA256\n 30:46:02:21:00:E6:5E:B5:34:70:3A:EE:D7:A6:40:6C:\n 35:5F:FE:97:AA:1A:48:C7:76:83:38:9D:76:4F:79:3D:\n 60:3C:E6:BA:15:02:21:00:8E:A1:3E:51:CB:3A:F6:01:\n 64:1C:D6:86:E6:B3:F4:48:5B:9B:27:80:EE:CB:E9:93:\n 95:15:69:41:AC:A9:98:93"},"validLeft":242},"apiVersion":2,"error":false}
curl --location --request GET 'https://zylalabs.com/api/5643/ssl+integrity+monitor+api/7348/verify+ssl?domain=amazon.com' --header 'Authorization: Bearer YOUR_API_KEY'
| 标头 | 描述 |
|---|---|
授权
|
[必需] 应为 Bearer access_key. 订阅后,请查看上方的"您的 API 访问密钥"。 |
无长期承诺。随时升级、降级或取消。 免费试用包括最多 50 个请求。
SSL完整性监控API旨在分析和验证网站的SSL证书,通过检查证书有效性、过期时间、加密协议和颁发机构,确保在传输过程中保护敏感数据
API 自动化证书审核 检测漏洞 并帮助保持对不断变化的安全标准的合规性 这对于防范网络威胁至关重要
您可以获取有关SSL证书有效性、到期日期、加密详情和证书颁发机关的信息
是的 SSL完整性监视器API提供基于JSON的响应,使其易于集成到您的工作流程和应用程序中
是的 SSL完整性监控API能够检测SSL配置中的漏洞帮助确保用户的安全连接
验证SSL端点返回有关SSL证书的有效性、到期状态、加密设置和签发者详细信息的数据。它包括字段,如`isvalidCertificate`、`expiry`、`issuer`和`certDetails`,提供关于证书安全性的全面见解
关键字段包括`isvalidCertificate`、`expiry`、`daysLeft`、`issuer`和`certDetails`。`certDetails`对象包含特定信息,如`name`、`serialNumber`、`validFrom`和`validTo`,这些信息对于理解证书的状态至关重要
响应数据以JSON格式构建,顶级对象包含布尔标志、过期细节和嵌套的`certDetails`对象。这种组织方式便于访问有关SSL证书的摘要和详细信息
验证SSL端点接受一个参数:网站URL 用户必须在请求中提供有效的URL以接收相应的SSL证书信息
用户可以利用返回的数据来评估SSL证书的有效性,监控到期日期,并确保符合安全标准。例如,`daysLeft`字段可以帮助在到期前安排续订
典型的用例包括自动化SSL证书审计监控证书过期和确保符合安全政策组织可以将API集成到他们的安全工作流程中以主动管理SSL配置
数据准确性通过定期更新和与可信证书颁发机构的检查来保持 API 实时验证 SSL 证书 确保提供的信息反映证书的当前状态
如果用户收到部分或空结果,他们应验证提供的 URL 的正确性,并确保该网站已安装 SSL 证书。此外,他们可以检查网络问题或稍后再试以确认证书的状态
服务级别:
100%
响应时间:
832ms
服务级别:
100%
响应时间:
1,045ms
服务级别:
100%
响应时间:
1,726ms
服务级别:
100%
响应时间:
841ms
服务级别:
100%
响应时间:
921ms
服务级别:
100%
响应时间:
505ms
服务级别:
100%
响应时间:
559ms
服务级别:
100%
响应时间:
800ms
服务级别:
100%
响应时间:
487ms
服务级别:
100%
响应时间:
532ms
服务级别:
100%
响应时间:
283ms
服务级别:
100%
响应时间:
666ms
服务级别:
100%
响应时间:
3,948ms
服务级别:
100%
响应时间:
4,330ms
服务级别:
100%
响应时间:
2,514ms
服务级别:
100%
响应时间:
417ms
服务级别:
100%
响应时间:
358ms
服务级别:
100%
响应时间:
299ms
服务级别:
100%
响应时间:
182ms
服务级别:
100%
响应时间:
601ms