3 ms·

You believe something false. I created amazingly secure dns zone entries glue records that are hosted on a cloud backbone. The very fact you cant see past that

You believe something false. I created amazingly secure dns zone entries glue records that are hosted on a cloud backbone. The very fact you cant see past that firewall of dns glue is proving the point of exactly how secure they are and how trustworthy the service is. Please educate yourself fully and dont jump to a conclusion like this. You really think I am running this out of my basement on bare metal or something? Would love to pentest this service since it is so early. I would be dumb not to. I guess I can transparently share the results of load at lets say 100k concurrent connections?

iscoelho 7y ago
Let's start dissecting this. ~ dig NS normail.co @ns1.cctld.co. ;; ADDITIONAL SECTION: ns1.box.normail.co. 3600 IN A 178.62.214.105 ns2.box.normail.co. 3600 IN A 178.62.214.105 ns1.cctld.co. is the registry server for the ".co" domain tld. Everyone has access to the glue records. It's how DNS works. They are not secure by any definition. You can also see for yourself at https://www.ultratools.com/tools/dnsLookup https://www.ultratools.com/tools/dnsLookup (in the Trace tab after you lookup) And your only MX record: normail.co. 3600 IN MX 10 box.normail.co. I'm honestly surprised you even have DNSSEC setup. That one hugely surprised me. And the host of 178.62.214.105? A single Digital Ocean VPS in Amsterdam. inetnum: 178.62.128.0 - 178.62.255.255 netname: DIGITALOCEAN-AMS-5 descr: DigitalOcean Amsterdam I'll accept that you're unaware of how the internet or cybersecurity works besides a primitive level as an explanation for the incoherent technobabble in your comment. I say this in the absolutely nicest way possible: please don't run a service where others rely on you when you know you are not capable of running a reliable service. There is a point where incompetency becomes malicious.

iscoelho 7y ago

Let's start dissecting this. ~ dig NS normail.co @ns1.cctld.co. ;; ADDITIONAL SECTION: ns1.box.normail.co. 3600 IN A 178.62.214.105 ns2.box.normail.co. 3600 IN A 178.62.214.105 ns1.cctld.co. is the registry server for the ".co" domain tld. Everyone has access to the glue records. It's how DNS works. They are not secure by any definition. You can also see for yourself at https://www.ultratools.com/tools/dnsLookup https://www.ultratools.com/tools/dnsLookup (in the Trace tab after you lookup) And your only MX record: normail.co. 3600 IN MX 10 box.normail.co. I'm honestly surprised you even have DNSSEC setup. That one hugely surprised me. And the host of 178.62.214.105? A single Digital Ocean VPS in Amsterdam. inetnum: 178.62.128.0 - 178.62.255.255 netname: DIGITALOCEAN-AMS-5 descr: DigitalOcean Amsterdam I'll accept that you're unaware of how the internet or cybersecurity works besides a primitive level as an explanation for the incoherent technobabble in your comment. I say this in the absolutely nicest way possible: please don't run a service where others rely on you when you know you are not capable of running a reliable service. There is a point where incompetency becomes malicious.