{"id":762,"date":"2020-03-19T10:52:00","date_gmt":"2020-03-19T10:52:00","guid":{"rendered":"https:\/\/sectigostore.com\/blog\/?p=762"},"modified":"2025-04-28T12:08:49","modified_gmt":"2025-04-28T12:08:49","slug":"ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors","status":"publish","type":"post","link":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/","title":{"rendered":"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><span class=\"break-word\">SSL_ERROR_RX_RECORD_TOO_LONG<\/span> &#8211; Not sure what this error is or why you\u2019re getting it? Here\u2019s what to know about it and how to get rid of it&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019re&nbsp;wondering how to bypass the &#8220;Secure Connection Failed&#8221; page with the&nbsp;\u201c<span class=\"break-word\">SSL_ERROR_RX_RECORD_TOO_LONG<\/span>\u201d&nbsp;error message,&nbsp;then&nbsp;you are in luck! In this article, we\u2019ll cover&nbsp;nine&nbsp;proven&nbsp;solutions&nbsp;for site visitors and admins that will help you&nbsp;avoid&nbsp;or fix this error.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s start with&nbsp;a few&nbsp;quick&nbsp;notes:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong><span class=\"break-word\">SSL_ERROR_RX_RECORD_TOO_LONG<\/span>&nbsp;is a server-side error.<\/strong>&nbsp;As a website visitor, you can&nbsp;only&nbsp;bypass this error or&nbsp;force browser to trust and open&nbsp;the website&nbsp;temporarily.&nbsp;Only a website owner can bring&nbsp;a permanent solution to this problem.&nbsp;&nbsp;<\/li><li><strong>This server-side error is experienced&nbsp;only in Firefox.<\/strong>&nbsp;However, even if you switch to another browser, it&#8217;ll just show a slightly different error message.<\/li><li><strong>The issue results from an SSL\/TLS certificate misconfiguration.<\/strong>&nbsp;If you are a website owner:&nbsp;SSL_ERROR_RX_RECORD_TOO_LONG&nbsp;indicates that you haven&#8217;t configured your <a href=\"https:\/\/sectigostore.com\/ssl-certificates\">TLS\/SSL certificate<\/a> properly. Please scroll down the article and check out the solution for the website-owner.&nbsp;&nbsp;<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How to Resolve&nbsp;<span class=\"break-word\">SSL_ERROR_RX_RECORD_TOO_LONG<\/span>&nbsp;as a Site Visitor&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These solutions are listed for website visitors&nbsp;only.&nbsp;You don\u2019t need to apply all of them. Just&nbsp;try&nbsp;them,&nbsp;one-by-one, until one finally works on your system and&nbsp;allows you to&nbsp;bypass the&nbsp;SSL_ERROR_RX_RECORD_TOO_LONG&nbsp;error page.&nbsp;&nbsp;&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution&nbsp;1: Configure the TLS Version Acceptance Level&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Some SSL certificates support&nbsp;the older <a href=\"https:\/\/sectigostore.com\/blog\/tls-version-1-3-what-to-know-about-the-latest-tls-version\/\">TLS versions<\/a> such&nbsp;as&nbsp;TLS&nbsp;1.1 or TLS 1.2.&nbsp;&nbsp;While&nbsp;Firefox&#8217;s&nbsp;security settings are configured in a way that it&nbsp;accepts&nbsp;only the latest&nbsp;TLS version,&nbsp;i.e. TLS 1.3.&nbsp;&nbsp;If Firefox encounters with the SSL certificate that supports old TLS version, it shows&nbsp;the&nbsp;SSL_ERROR_RX_RECORD_TOO_LONG&nbsp;error.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By changing the Firefox\u2019s TLS acceptance level, you&nbsp;can make it&nbsp;accept the&nbsp;websites that use SSL certificates supporting older&nbsp;TLS version.&nbsp;This is the safest&nbsp;method&nbsp;to&nbsp;bypass&nbsp;SSL_ERROR_RX_RECORD_TOO_LONG error&nbsp;because you will&nbsp;be&nbsp;still&nbsp;accessing&nbsp;the website that encrypts the data using&nbsp;an HTTPS&nbsp;protocol.&nbsp;&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Write \u201cabout:config&#8221; in the Firefox address bar.&nbsp;<\/li><li>Click on the&nbsp;<strong>I accept the risk<\/strong>&nbsp;button.&nbsp;<\/li><li>Now, search for &#8220;security.tls.version.max&#8221; and double click on it.<\/li><li>Set&nbsp;<strong>security.tls.version.max&nbsp;<\/strong>as \u201c3.\u201d&nbsp;<\/li><li>Search \u201csecurity.tls.version.min\u201d in the search box and double click it.&nbsp;<\/li><li>Set&nbsp;<strong>security.tls.version.min&nbsp;<\/strong>as \u201c0.\u201d&nbsp; <\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"336\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image.jpeg\" alt=\"Screenshot of the about:config window in Firefox with a possible solution to fix the SSL_ERROR_RX_RECORD_TOO_LONG message\" class=\"wp-image-763 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image.jpeg 1024w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-300x98.jpeg 300w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-560x184.jpeg 560w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-940x308.jpeg 940w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">By doing this, you\u2019re instructing Firefox to accept the websites that are running on any TLS version, including on TLS 1.1, TLS 1.2, TLS 1.3, and TLS 1.0.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If this tip&nbsp;doesn\u2019t&nbsp;work, move to the next&nbsp;solution.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution 2: Clear Browsing History and Cache Memory&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Sometimes, the website owner has already resolved the SSL_ERROR_RX_RECORD_TOO_LONG error on the server side, but Firefox\u2019s cache memory is still displaying old information. Clearing your browsing history, cookies, and cache memory might resolve this issue:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Open Firefox and navigate to\u202f<strong>Options<\/strong>\u202ffrom the top-right drop-down menu.&nbsp;<\/li><li>Go to<strong>\u202fPrivacy and Security\u202f<\/strong>from the left menu bar.&nbsp;<\/li><li>Click on<strong>\u202fClear Data\u202f<\/strong>in the\u202f<strong>Cookies and Site Data<\/strong>\u202fsection.&nbsp;<\/li><li>Select\u202f<strong>Clear History.<\/strong>&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"646\" height=\"405\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-9.png\" alt=\"Screenshot of the Cookies and Site Data window\" class=\"wp-image-773 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-9.png 646w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-9-300x188.png 300w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-9-560x351.png 560w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-9-480x300.png 480w\" sizes=\"auto, (max-width: 646px) 100vw, 646px\" \/><\/figure><\/div>\n\n\n\n<ul class=\"wp-block-list\"><li>Select all the options and click on<strong>\u202fClear Now.<\/strong>&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"559\" height=\"493\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-4.png\" alt=\"Screenshot of the Clear All History window\" class=\"wp-image-768 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-4.png 559w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-4-300x265.png 300w\" sizes=\"auto, (max-width: 559px) 100vw, 559px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\"> <strong>Note:&nbsp;From this point on, all of the site visitor solutions are&nbsp;risky&nbsp;because&nbsp;you will be accessing the website&nbsp;that&nbsp;has a misconfigured SSL\/TLS certificate and&nbsp;is transferring&nbsp;your&nbsp;data using unsecured HTTP channel.&nbsp;Use them only when you are 100% sure that website you are approaching is safe!&nbsp;<\/strong>&nbsp; <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution&nbsp;3: Trusted Sites Configuration&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When you add a website in your \u201ctrusted site\u201d list, all the browsers will trust it&nbsp;regardless&nbsp;of its SSL\/TLS configuration.&nbsp;&nbsp;To add a site to your trusted site list:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Search&nbsp;<strong>Internet Options<\/strong>&nbsp;in your Windows search bar.&nbsp;<\/li><li>In the&nbsp;<strong>Internet Properties<\/strong>&nbsp;window,&nbsp;click on the&nbsp;<strong>Security<\/strong>&nbsp;tab.&nbsp;<\/li><li>Select&nbsp;<strong>Trusted Sites<\/strong>.&nbsp;<\/li><li>Click on the&nbsp;<strong>Sites<\/strong>&nbsp;button&nbsp;\u2014&nbsp;a new window will pop-up.&nbsp;<\/li><li>Manually add the URL of the website that\u2019s&nbsp;displaying the error message.&nbsp;Select&nbsp;<strong>Add<\/strong>&nbsp;and then&nbsp;<strong>Close<\/strong>.&nbsp;&nbsp;<\/li><li>Back in the Internet Properties window, click&nbsp;<strong>Apply<\/strong>&nbsp;and&nbsp;<strong>OK<\/strong>.&nbsp;That\u2019s it!&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"876\" height=\"563\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-10.png\" alt=\"Screenshot of the Internet Properties window and Trusted Sites window\" class=\"wp-image-774 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-10.png 876w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-10-300x193.png 300w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-10-560x360.png 560w\" sizes=\"auto, (max-width: 876px) 100vw, 876px\" \/><\/figure><\/div>\n\n\n\n<h3 class=\"wp-block-heading\">Solution&nbsp;4: Shift to Using the HTTP Protocol&nbsp;&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the easiest solutions for SSL_ERROR_RX_RECORD_TOO_LONG error is to shift from HTTPS to HTTP protocol.&nbsp;<strong>Note:<\/strong>&nbsp;We\u2019re informing you that this is an option to get rid of the error. However, it\u2019s&nbsp;<em>not<\/em>&nbsp;an ideal solution to ever connect to a website using the insecure HTTP protocol because it leaves you at risk.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the website does not have a 301 redirect, then only this solution will work.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the address bar, the website you are trying to open will be starting with&nbsp;<strong>HTTPS<\/strong><strong>:\/\/<\/strong>. Simply remove the letter \u201cs\u201d from HTTPS:\/\/ and open the website using HTTP:\/\/.&nbsp;&nbsp;<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"210\" height=\"30\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image.png\" alt=\"screenshot of the firefox web address bar\" class=\"wp-image-764 addshadow\"><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">However, this solution might not work if the website has already redirected to the HTTPS. If that is the case, move on to the next solution.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution&nbsp;5:&nbsp;Open the Website&nbsp;in Safe Mode&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Sometimes,&nbsp;the security add-ons don&#8217;t open&nbsp;websites&nbsp;using&nbsp;misconfigured SSL certificates. When you restart Firefox in safe mode, all the add-ons&nbsp;are&nbsp;disabled, and you\u2019ll&nbsp;be able to access the site.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To start Firefox in safe mode:&nbsp;Click on the&nbsp;browser menu&nbsp;(three lines on the right&nbsp;side&nbsp;of the window).&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Navigate&nbsp;to&nbsp;<strong>Help<\/strong>.&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"282\" height=\"689\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-7.png\" alt=\"A screenshot of the Firefox menu with help selected\" class=\"wp-image-771 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-7.png 282w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-7-123x300.png 123w\" sizes=\"auto, (max-width: 282px) 100vw, 282px\" \/><\/figure><\/div>\n\n\n\n<ul class=\"wp-block-list\"><li>Select&nbsp;<strong>Restart with Add-ons Disabled\u2026<\/strong>&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"266\" height=\"274\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-1.png\" alt=\"screenshot of the Firefox menu\" class=\"wp-image-765 addshadow\"><\/figure><\/div>\n\n\n\n<ul class=\"wp-block-list\"><li>Select the&nbsp;<strong>Restart<\/strong>&nbsp;Tab&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"382\" height=\"137\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-2.png\" alt=\"Screenshot of the restart pop-up\" class=\"wp-image-766 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-2.png 382w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-2-300x108.png 300w\" sizes=\"auto, (max-width: 382px) 100vw, 382px\" \/><\/figure><\/div>\n\n\n\n<ul class=\"wp-block-list\"><li>Click on&nbsp;<strong>Start in Safe Mode.<\/strong>&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"401\" height=\"194\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-3.png\" alt=\"screenshot of the Firefox safe mode window\" class=\"wp-image-767 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-3.png 401w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-3-300x145.png 300w\" sizes=\"auto, (max-width: 401px) 100vw, 401px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s it! If it worked, congratulations. If not, let\u2019s try the next method.&nbsp;&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution&nbsp;6: Change&nbsp;Your&nbsp;Proxy Settings&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Sometimes the wrong proxy connections can also cause&nbsp;the&nbsp;SSL_ERROR_RX_RECORD_TOO_LONG&nbsp;message to display.&nbsp;You can disable proxy settings to check whether it is the culprit&nbsp;that causes this error&nbsp;by doing the following:&nbsp;&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Go to&nbsp;Firefox&nbsp;menu and click on&nbsp;<strong>Options.&nbsp;<\/strong>&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"266\" height=\"449\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-5.png\" alt=\"Screenshot of the Firefox menu\" class=\"wp-image-769 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-5.png 266w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-5-178x300.png 178w\" sizes=\"auto, (max-width: 266px) 100vw, 266px\" \/><\/figure><\/div>\n\n\n\n<ul class=\"wp-block-list\"><li>Locate&nbsp;<strong>Network Settings<\/strong>&nbsp;and click on&nbsp;<strong>Settings<\/strong>.&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"702\" height=\"131\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-6.png\" alt=\"screenshot of the network settings window\" class=\"wp-image-770 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-6.png 702w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-6-300x56.png 300w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-6-560x105.png 560w\" sizes=\"auto, (max-width: 702px) 100vw, 702px\" \/><\/figure><\/div>\n\n\n\n<ul class=\"wp-block-list\"><li>Select&nbsp;<strong>No Proxy<\/strong>&nbsp;option. Click&nbsp;<strong>OK<\/strong>&nbsp;and restart the browser.&nbsp;&nbsp;<\/li><\/ul>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"774\" height=\"244\" src=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-8.png\" alt=\"screenshot of the connection settings window\" class=\"wp-image-772 addshadow\" srcset=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-8.png 774w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-8-300x95.png 300w, https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/image-8-560x177.png 560w\" sizes=\"auto, (max-width: 774px) 100vw, 774px\" \/><\/figure><\/div>\n\n\n\n<h3 class=\"wp-block-heading\">Solution 7:&nbsp;Temporarily&nbsp;Disable Your Antivirus and Firewall&nbsp;&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most of&nbsp;antivirus software and firewalls have SSL scanning&nbsp;capabilities. So, even after you have instructed browsers to bypass the SSL related errors, the antivirus program would still block the websites with misconfigured SSL certificates.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Just go to your antivirus software or firewall and search for the SSL related settings. It could be named as&nbsp;\u201c<strong>HTTPS Scanning,\u201d \u201cScan SSL,\u201d<\/strong>\u202f\u201c<strong>show the safe result<\/strong>,&#8221; &#8220;<strong>Do not scan encrypted connections,\u201d<\/strong><strong>&nbsp;<\/strong>etc.&nbsp;disable such settings.&nbsp;If you don\u2019t find any such setting area, you can disable the antivirus\/firewall temporarily.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Note:<\/strong>&nbsp;Disabling&nbsp;your&nbsp;antivirus and&nbsp;firewall&nbsp;is a risky step&nbsp;\u2014 one that we never recommend.&nbsp;If you decide to try this option, be sure to reactivate&nbsp;the solution(s) you disable&nbsp;after you get access to the website you want.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Well, that\u2019s the end of it. Now, it\u2019s time to move on to helping site owners and admins fix this issue with their sites.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">SSL_ERROR_RX_RECORD_TOO_LONG&nbsp;as a&nbsp;Website Owner&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As we mentioned above,&nbsp;SSL_ERROR_RX_RECORD_TOO_LONG&nbsp;is a&nbsp;server-side&nbsp;error.&nbsp;This&nbsp;means&nbsp;that&nbsp;only you&nbsp;\u2014&nbsp;the website owner&nbsp;or&nbsp;webmaster&nbsp;\u2014&nbsp;can&nbsp;resolve&nbsp;this error&nbsp;with one of the&nbsp;following&nbsp;solutions&nbsp;listed below.&nbsp;&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution&nbsp;1: Configure&nbsp;the&nbsp;Listening Port&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Without an SSL\/TKS&nbsp;certificate, all the traffic between a browser and&nbsp;your&nbsp;server travels using&nbsp;the&nbsp;port 80&nbsp;(also called&nbsp;the&nbsp;\u201clistening port\u201d). When you install an SSL certificate on your server, it enables port 443 for data transmission, which&nbsp;allows&nbsp;you to use the&nbsp;secure&nbsp;HTTPS protocol.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you haven\u2019t configured your SSL certificate properly&nbsp;to&nbsp;support&nbsp;the&nbsp;use of&nbsp;port 443,&nbsp;then any&nbsp;web traffic&nbsp;for the site will&nbsp;faces obstacles to pass through&nbsp;it.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">All the servers have different ways&nbsp;to configure the TLS\/SSL certificate.&nbsp;Below&nbsp;are&nbsp;the links&nbsp;for Apache and Linux.&nbsp;&nbsp;&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>How&nbsp;to&nbsp;<a href=\"https:\/\/httpd.apache.org\/docs\/2.4\/bind.html\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"configure SSL listening port in Apache (opens in a new tab)\">configure SSL listening port in Apache<\/a>&nbsp;<\/li><li>How&nbsp;to&nbsp;<a href=\"https:\/\/linuxconfig.org\/ubuntu-20-04-open-http-port-80-and-https-port-443-with-ufw\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"configure SSL listening port in Linux (opens in a new tab)\">configure SSL listening port in Linux<\/a>&nbsp;<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019re&nbsp;using other servers, please search \u201cPort 443 + HTTPS&nbsp;+ Your server&nbsp;name\u201d to&nbsp;find&nbsp;additional&nbsp;resources.&nbsp;&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution&nbsp;2: Update&nbsp;Your&nbsp;TLS\/SSL Library&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">SSL_ERROR_RX_RECORD_TOO_LONG&nbsp;can also appear&nbsp;when your server\/system doesn\u2019t support&nbsp;your&nbsp;TLS&nbsp;version.&nbsp;You can tackle this issue by updating the SSL library in&nbsp;<a href=\"https:\/\/www.openssl.org\/\" target=\"_blank\" rel=\"noreferrer noopener\">OpenSSL<\/a>.&nbsp;Most browsers already support TLS 1.3, and many servers are working on upgrading to support it.&nbsp;So, make sure TLS 1.3 is enabled.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If nothing else:&nbsp;&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>ensure you\u2019re&nbsp;supporting&nbsp;TLS 1.2&nbsp;at&nbsp;the&nbsp;minimum,&nbsp;and&nbsp;<\/li><li>disable&nbsp;any deprecated versions (such as SSL 3.0 and TLS 1.0, and&nbsp;<a href=\"https:\/\/hacks.mozilla.org\/2020\/02\/its-the-boot-for-tls-1-0-and-tls-1-1\/\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"TLS 1.1 after March 2020 (opens in a new tab)\">TLS 1.1 after March 2020<\/a>)&nbsp;immediately.&nbsp;<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">A Final Word&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If&nbsp;you are a website visitor and&nbsp;have&nbsp;decided to&nbsp;proceed&nbsp;further with any unsecured solutions to access the website, be careful. Don\u2019t share any financial&nbsp;information such as payment card numbers, bank account numbers or any personally identifiable information (PII) such as&nbsp;email address, phone number, physical address, social security number, etc.,&nbsp;on such website.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">SSL_ERROR_RX_RECORD_TOO_LONG is a server side error and when you force your browser to ignore it,&nbsp;you will be approaching a website that\u2019s not encrypting your data and&nbsp;hence, making it vulnerable for data theft and man-in-the-middle attacks.&nbsp;&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SSL_ERROR_RX_RECORD_TOO_LONG &#8211; Not sure what this error is or why you\u2019re getting it? Here\u2019s what to know about it and how to get rid of it&nbsp; If you\u2019re&nbsp;wondering how to&#8230;<\/p>\n","protected":false},"author":6,"featured_media":779,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","tve_updated_post":"","tve_custom_css":"","tve_user_custom_css":"","tve_globals":{},"tcb2_ready":1,"tcb_editor_enabled":0,"tve_landing_page":"","_tve_header":"","_tve_footer":""},"categories":[13],"tags":[48],"class_list":["post-762","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cyber-security","tag-errors","post-with-tags"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors - InfoSec Insights<\/title>\n<meta name=\"description\" content=\"If you\u2019re wondering how to fix or bypass the \u201cSSL_ERROR_RX_RECORD_TOO_LONG\u201d error?We\u2019ll cover nine proven solutions that will help you avoid this error.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors - InfoSec Insights\" \/>\n<meta property=\"og:description\" content=\"If you\u2019re wondering how to fix or bypass the \u201cSSL_ERROR_RX_RECORD_TOO_LONG\u201d error?We\u2019ll cover nine proven solutions that will help you avoid this error.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/\" \/>\n<meta property=\"og:site_name\" content=\"InfoSec Insights\" \/>\n<meta property=\"article:published_time\" content=\"2020-03-19T10:52:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-04-28T12:08:49+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t<meta property=\"og:image:height\" content=\"1000\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Medha Mehta\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Medha Mehta\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/\"},\"author\":{\"name\":\"Medha Mehta\",\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/#\\\/schema\\\/person\\\/41d095943b7798ade1bc3683c8822f15\"},\"headline\":\"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors\",\"datePublished\":\"2020-03-19T10:52:00+00:00\",\"dateModified\":\"2025-04-28T12:08:49+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/\"},\"wordCount\":1915,\"image\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/03\\\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg\",\"keywords\":[\"errors\"],\"articleSection\":[\"Cyber Security\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/\",\"url\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/\",\"name\":\"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors - InfoSec Insights\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/03\\\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg\",\"datePublished\":\"2020-03-19T10:52:00+00:00\",\"dateModified\":\"2025-04-28T12:08:49+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/#\\\/schema\\\/person\\\/41d095943b7798ade1bc3683c8822f15\"},\"description\":\"If you\u2019re wondering how to fix or bypass the \u201cSSL_ERROR_RX_RECORD_TOO_LONG\u201d error?We\u2019ll cover nine proven solutions that will help you avoid this error.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/#primaryimage\",\"url\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/03\\\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg\",\"contentUrl\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/03\\\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg\",\"width\":1600,\"height\":1000,\"caption\":\"Graphic representing the Connection Failed error message that results from SSL_ERROR_RX_RECORD_TOO_LONG\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/\",\"name\":\"InfoSec Insights\",\"description\":\"SectigoStore.com Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/sectigostore.com\\\/blog\\\/#\\\/schema\\\/person\\\/41d095943b7798ade1bc3683c8822f15\",\"name\":\"Medha Mehta\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a1e5b5025e87d4e1acfd683fbede8c366e652e9ddb2164b7a0d0a77e2d9da727?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a1e5b5025e87d4e1acfd683fbede8c366e652e9ddb2164b7a0d0a77e2d9da727?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a1e5b5025e87d4e1acfd683fbede8c366e652e9ddb2164b7a0d0a77e2d9da727?s=96&d=mm&r=g\",\"caption\":\"Medha Mehta\"},\"description\":\"Medha is a regular contributor to InfoSec Insights. She's a tech enthusiast and writes about technology, website security, cryptography, cyber security, and data protection.\",\"sameAs\":[\"https:\\\/\\\/sectigostore.com\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors - InfoSec Insights","description":"If you\u2019re wondering how to fix or bypass the \u201cSSL_ERROR_RX_RECORD_TOO_LONG\u201d error?We\u2019ll cover nine proven solutions that will help you avoid this error.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/","og_locale":"en_US","og_type":"article","og_title":"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors - InfoSec Insights","og_description":"If you\u2019re wondering how to fix or bypass the \u201cSSL_ERROR_RX_RECORD_TOO_LONG\u201d error?We\u2019ll cover nine proven solutions that will help you avoid this error.","og_url":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/","og_site_name":"InfoSec Insights","article_published_time":"2020-03-19T10:52:00+00:00","article_modified_time":"2025-04-28T12:08:49+00:00","og_image":[{"width":1600,"height":1000,"url":"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg","type":"image\/jpeg"}],"author":"Medha Mehta","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Medha Mehta","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/#article","isPartOf":{"@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/"},"author":{"name":"Medha Mehta","@id":"https:\/\/sectigostore.com\/blog\/#\/schema\/person\/41d095943b7798ade1bc3683c8822f15"},"headline":"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors","datePublished":"2020-03-19T10:52:00+00:00","dateModified":"2025-04-28T12:08:49+00:00","mainEntityOfPage":{"@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/"},"wordCount":1915,"image":{"@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/#primaryimage"},"thumbnailUrl":"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg","keywords":["errors"],"articleSection":["Cyber Security"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/","url":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/","name":"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors - InfoSec Insights","isPartOf":{"@id":"https:\/\/sectigostore.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/#primaryimage"},"image":{"@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/#primaryimage"},"thumbnailUrl":"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg","datePublished":"2020-03-19T10:52:00+00:00","dateModified":"2025-04-28T12:08:49+00:00","author":{"@id":"https:\/\/sectigostore.com\/blog\/#\/schema\/person\/41d095943b7798ade1bc3683c8822f15"},"description":"If you\u2019re wondering how to fix or bypass the \u201cSSL_ERROR_RX_RECORD_TOO_LONG\u201d error?We\u2019ll cover nine proven solutions that will help you avoid this error.","breadcrumb":{"@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/#primaryimage","url":"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg","contentUrl":"https:\/\/sectigostore.com\/blog\/wp-content\/uploads\/2020\/03\/bigstock-Broken-Old-String-Risk-And-A-232607839.jpg","width":1600,"height":1000,"caption":"Graphic representing the Connection Failed error message that results from SSL_ERROR_RX_RECORD_TOO_LONG"},{"@type":"BreadcrumbList","@id":"https:\/\/sectigostore.com\/blog\/ssl_error_rx_record_too_long-9-solutions-for-site-owners-and-visitors\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sectigostore.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SSL_ERROR_RX_RECORD_TOO_LONG: 9 Solutions for Site Owners and Visitors"}]},{"@type":"WebSite","@id":"https:\/\/sectigostore.com\/blog\/#website","url":"https:\/\/sectigostore.com\/blog\/","name":"InfoSec Insights","description":"SectigoStore.com Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sectigostore.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/sectigostore.com\/blog\/#\/schema\/person\/41d095943b7798ade1bc3683c8822f15","name":"Medha Mehta","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a1e5b5025e87d4e1acfd683fbede8c366e652e9ddb2164b7a0d0a77e2d9da727?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a1e5b5025e87d4e1acfd683fbede8c366e652e9ddb2164b7a0d0a77e2d9da727?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a1e5b5025e87d4e1acfd683fbede8c366e652e9ddb2164b7a0d0a77e2d9da727?s=96&d=mm&r=g","caption":"Medha Mehta"},"description":"Medha is a regular contributor to InfoSec Insights. She's a tech enthusiast and writes about technology, website security, cryptography, cyber security, and data protection.","sameAs":["https:\/\/sectigostore.com\/"]}]}},"_links":{"self":[{"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/posts\/762","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/comments?post=762"}],"version-history":[{"count":0,"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/posts\/762\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/media\/779"}],"wp:attachment":[{"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/media?parent=762"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/categories?post=762"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sectigostore.com\/blog\/wp-json\/wp\/v2\/tags?post=762"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}