Test your Key answers:

[treasurer]

Hello new people to the hunt.

It's not real obvious at first, but Lukas has provided this link to test your KEY solves.

You can also see all of the videos pertaining to the hunt:

digitalburiedtreasure.com/dbt-1-1000-prize/

As of 11/18/2019, none of us knows where the real treasure chest is. You can still be the first.

Please visit the threads for each stanza and bring your ideas!

[susb8383]

Apparently the key tester is case-sensitive. Not what I was expecting.

[jewelie]

Susb....um, how do you know it I case sensitive???

[goldenchild]

Dec 1, 2019 22:01:58 GMT -5 susb8383 said:

Apparently the key tester is case-sensitive. Not what I was expecting.

the only way to know that is if you actually entered a correct answer at some point??? Have you found a key !?!?

[luna]

He answered that it was case sensitive in a reply to a comment on the original Digital Buried Treasure YouTube video.

[treasurer]

Dec 1, 2019 22:03:59 GMT -5 jewelie said:

Susb....um, how do you know it I case sensitive???

Lukas was asked if the key-tester was case sensitive about a week ago on the YouTube comments. He answered "Yes" about a day ago (today is 12/1/2019). 

Edit: Sorry luna, you already answered the question while I was writing this.

[susb8383]

Which is kind of strange. We all know Key 1 is a number, so case wouldn't matter. But does this imply that Key 2 is a proper noun?

[luna]

Dec 2, 2019 8:30:20 GMT -5 susb8383 said:

Which is kind of strange. We all know Key 1 is a number, so case wouldn't matter. But does this imply that Key 2 is a proper noun?

I also wouldn’t put it past Lukas to answer the question, but for it to not be relevant. I.e., it really is case sensitive, but that doesn’t really matter because there aren’t any capital letters anyway.

[captnkush]

If the first key is a 10 digit number...presumably a phone number does that mean we need to also enter the () for the area code and the - btwn the prefix and the last 4 so it reads (xxx)xxx-xxxx . I really hope not . But if the keys are case sensitive is that something we overlooked?

[susb8383]

I doubt it. 1234567890 is still a phone number. And didn’t efanton specifically ask if key 1 is a 10-digit number?

[susb8383]

I bet luna is right. Any pw field is going to be case-sensitive even if it doesn’t matter.

[susb8383]

Uh-oh! Be careful if you want to test a lot of possibilities at once. I was testing a bunch of keys one at a time. I probably did about 400 or so without a problem. But then all of a sudden I got a 403 error, Forbidden. At first I thought I stumbled upon the correct key, but when I retested one that didn't work, I got the same error.

So maybe the website thinks I'm a spammer or something and has blocked my IP. D'oh!!! I'm not sure how to fix it. I tried clearing my browser cache but it didn't help.

[efanton]

Dec 21, 2019 22:34:16 GMT -5 susb8383 said:

Uh-oh! Be careful if you want to test a lot of possibilities at once. I was testing a bunch of keys one at a time. I probably did about 400 or so without a problem. But then all of a sudden I got a 403 error, Forbidden. At first I thought I stumbled upon the correct key, but when I retested one that didn't work, I got the same error.

So maybe the website thinks I'm a spammer or something and has blocked my IP. D'oh!!! I'm not sure how to fix it. I tried clearing my browser cache but it didn't help.

You need to make sure you delete any cookies for digitalburiedtreasure.com

Clearing your cache/browser history  alone will not help.

www.howtogeek.com/304218/how-to-clear-your-history-in-any-browser/


This can also happen if somehow you have modified the URL by mistake in your browser (mouse drag,  typing thinking you are in a different window etc).  Easy to do and not realise it.  Just go back to digitalburiedtreasure.com and follow the links back to the key checker


It can also happen if the server is getting hit heavily by requests, or a service or daemon on the server stops.  Nothing you can do about this except wait a few hours for either the server to recover or the site admin to restart the services or reboot the server.

I have just checked and the server is up and running properly at the time of this post.


Hope the above helps.

[susb8383]

I wonder if it is something with the site. It comes and goes. Yesterday it worked again and i tested about 20. Then I got the error again. Clearing cookies and the cache didn’t help. I wonder if someone is using a program to crunch through millions of combinations and it’s bringing things down...is that possible?

[efanton]

Dec 23, 2019 7:51:57 GMT -5 susb8383 said:

I wonder if it is something with the site. It comes and goes. Yesterday it worked again and i tested about 20. Then I got the error again. Clearing cookies and the cache didn’t help. I wonder if someone is using a program to crunch through millions of combinations and it’s bringing things down...is that possible?

Yes a server will stop taking requests if its services/daemons buffer or cache are full. 
A typical server should handle many many requests per second so if it is taking huge numbers of requests this is extremely unlikely to happen by someone entering numbers manually.
It could happen if someone has programmed an automated 'attack' on the server.  If this is the case then its a really sloppy approach as the obvious thing to do would be to put a small random time interval between requests. 
with a 10 digit number it would require up to 1 Billion attempts to automate a incremental search for the 1st key to guarantee getting the right answer. 
! billion is a much bigger number than most people realise.  1 billion seconds would be in excess of 31 years.  Even if a server could handle hundreds of request per second it would still take over 4 months continuous.