From 6d8a64423f90af92652c54a428314c4bf40b250f Mon Sep 17 00:00:00 2001
From: david <david@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Fri, 28 Apr 2017 18:43:38 +0000
Subject: [PATCH] dnscurve.org has https.

---
 scripts/dns-nsec3-enum.nse | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/dns-nsec3-enum.nse b/scripts/dns-nsec3-enum.nse
index a0e4d2b83..03fbd97de 100644
--- a/scripts/dns-nsec3-enum.nse
+++ b/scripts/dns-nsec3-enum.nse
@@ -19,7 +19,7 @@ with salt and number of iterations used. This technique is known as
 "NSEC3 walking".
 
 That info should then be fed into an offline cracker, like
-<code>unhash</code> from http://dnscurve.org/nsec3walker.html, to
+<code>unhash</code> from https://dnscurve.org/nsec3walker.html, to
 bruteforce the actual names from the hashes. Assuming that the script
 output was written into a text file <code>hashes.txt</code> like:
 <code>
@@ -46,7 +46,7 @@ Use the <code>dns-nsec-enum</code> script to handle servers that use NSEC
 rather than NSEC3.
 
 References:
-* http://dnscurve.org/nsec3walker.html
+* https://dnscurve.org/nsec3walker.html
 ]]
 ---
 -- @usage