From ae6701f19ca660db0fa8e5bdeb862d834f4b193f Mon Sep 17 00:00:00 2001
From: zenithium <48525551+zenithium@users.noreply.github.com>
Date: Sun, 8 Mar 2020 02:02:15 +0000
Subject: [PATCH] Removed second test button

---
 _includes/sections/browser-webrtc.html | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/_includes/sections/browser-webrtc.html b/_includes/sections/browser-webrtc.html
index 3a56b068..f001b47a 100644
--- a/_includes/sections/browser-webrtc.html
+++ b/_includes/sections/browser-webrtc.html
@@ -49,10 +49,6 @@
   <li>In the drop-down menu, open the "WebRTC" submenu and ensure "Enable Legacy WebRTC API" is unchecked. If it's grayed out, even better.</li>
 </ol>
 
-<p>
-<a class="btn btn-primary" target="_blank" rel="noopener noreferrer" href="https://ipleak.net">Test your Browser again</a>
-</p>
-
 <h3>How to disable WebRTC in Google Chrome?</h3>
 
 <p>WebRTC cannot be fully disabled in Chrome; however, it is possible to change its routing settings (and prevent leaks) using an extension. Two open-source solutions include <a href="https://chrome.google.com/webstore/detail/webrtc-leak-prevent/eiadekoaikejlgdbkbdfeijglgfdalml">WebRTC Leak Prevent</a> (options may need to be changed depending on the scenario), and <a href="https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm">uBlock Origin</a> (select "Prevent WebRTC from leaking local IP addresses" in Settings).</p>