Quote:
Originally Posted by bluntroller
simply spoken...
I call the website hmamail.com (which is invalid, no DNS-Entry
|
Untrue. See below.
Quote:
Originally Posted by ondoho
i get the same.
but why?
this is so weird.
'whois hmamail.com' gives very elaborate output about it being some godaddy site in arizona...
|
"some GoDaddy site in Arizona" is the
Domain Registry.
It makes sense that if you run a proxy anonymizer and want to send email from that same service,
that you as a network and system administrator, set hmamail.com to only resolve to a working
email host from a known host. Not resolvable from the outside. I think it's easily done too, eg:
Set
A Records to 127.0.0.1 on the name servers, (theirs are in Amazon's Route 53) DNS service:
Code:
dig A +short hmamail.com @ns-1016.awsdns-63.net
feel free to try a couple more.
Code:
host -t ns hmamail.com
hmamail.com name server ns-1016.awsdns-63.net.
hmamail.com name server ns-1072.awsdns-06.org.
hmamail.com name server ns-166.awsdns-20.com.
hmamail.com name server ns-1839.awsdns-37.co.uk
Short version:
On their page/service, the site can resolve hmamail.com and likely authenticates to another email service
to process for delivery as (example)
inbound@hmamail.com
Some DNS detective work can be used to make the same conclusion.
Code:
dig MX +short hmamail.com
0 inbound.hmamail.com.
shows us the mail server identifying host(s)
Code:
host inbound.hmamail.com
inbound.hmamail.com has address 96.44.163.218
and that turns out to be on
QuadraNet, Inc
It is conceivable that inbound.hmamail.com will only receive mail from hidemyass.com and that via "Trusted Hosts".
Good stuff on a Saturday.