Jun 05, 2016, 04:51 am
(This post was last modified: Jun 05, 2016, 07:33 am by N4NC3Y. Edited 1 time in total.)
Namecoin has an API where you can query entries. I have it on one of my computers but that's not great for my grandpapy. Luckily there is an experimental online one at api.namecoin.org.
If you decode the output you get:
That's not much good. All it gives are a couple name server records which we wouldn't need if DNS wasn't blocked and can't use if it is (the .bit address is not resolvable, by the way). It also doesn't contain the SSL certificate fingerprint which would be useful for verifying the sites authenticity when new addresses are spawned.
I think I know the answer but I will ask anyway.
Are there any plans to update the Namecoin entry with information we can use to bypass in-band DNS?
If you decode the output you get:
Code:
{
"name" : "d/thepiratebay",
"vout" : 1,
"expires_in" : 21871,
"value" : "{\"ns\": [\"ns1.domaincoin.net\", \"ns2.domaincoin.net\"]}",
"height" : 275071,
"address" : "MySw3cS1HRzRTBeP6FnAbfZQybq4c8bPuP",
"txid" : "632a1479d7baef30c97d5eb0a619b396437b12a3f4425547011f7c1f5c99d7e3",
"expired" : false
}That's not much good. All it gives are a couple name server records which we wouldn't need if DNS wasn't blocked and can't use if it is (the .bit address is not resolvable, by the way). It also doesn't contain the SSL certificate fingerprint which would be useful for verifying the sites authenticity when new addresses are spawned.
I think I know the answer but I will ask anyway.
Are there any plans to update the Namecoin entry with information we can use to bypass in-band DNS?