DNS Spy
Connectivity: 100%
The following nameservers are available and responding correctly for DNS queries for your domain m-d.net.
| Nameserver | IP address(es) | SOA serial |
|---|---|---|
| anyns1.m-d.net. |
45.127.112.20
2620:95:4001::1 |
2019041104 |
| anyns2.m-d.net. |
45.127.113.20
2620:95:4002::2 |
2019041104 |
| ns.m-d.net. | 35.226.188.118 | 2019041104 |
| puck.nether.net. |
204.42.254.5
2001:418:3f4::5 |
2019041104 |
Good news, no warnings or errors were found.
We could not find any recommendations at this time.
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- All nameservers reply with the same SOA serial number.
- The nameserver IPs are distributed across multiple subnets.
- All nameservers are online.
- Nameservers are available over IPv4.
- Nameservers are available over IPv6.
Performance: 100%
We tested each nameserver and measured the following response times.
| Nameserver | IP address(es) | Response time |
|---|---|---|
| anyns1.m-d.net. |
45.127.112.20
2620:95:4001::1 |
105ms
114ms |
| anyns2.m-d.net. |
45.127.113.20
2620:95:4002::2 |
105ms
103ms |
| ns.m-d.net. | 35.226.188.118 | 106ms |
| puck.nether.net. |
204.42.254.5
2001:418:3f4::5 |
104ms
99ms |
Good news, no warnings or errors were found.
We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.
- Nameserver anyns1.m-d.net. (45.127.112.20) replied reasonably fast (< 150ms), but you should aim for < 50ms response times.
- Nameserver anyns2.m-d.net. (45.127.113.20) replied reasonably fast (< 150ms), but you should aim for < 50ms response times.
- Nameserver ns.m-d.net. (35.226.188.118) replied reasonably fast (< 150ms), but you should aim for < 50ms response times.
- Nameserver puck.nether.net. (204.42.254.5) replied reasonably fast (< 150ms), but you should aim for < 50ms response times.
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- Nameserver anyns1.m-d.net. (2620:95:4001::1) replied in a reasonable time.
- Nameserver anyns2.m-d.net. (2620:95:4002::2) replied in a reasonable time.
- Nameserver puck.nether.net. (2001:418:3f4::5) replied in a reasonable time.
Resilience & Security: 86%
These are the locations and providers of your nameservers.
| Nameserver | Location | ISP |
|---|---|---|
| anyns1.m-d.net. |
IPv4: HK
IPv6: US |
AS40138 - MDNET - Mach Dilemma, LLC, US
AS40138 - MDNET - Mach Dilemma, LLC, US |
| anyns2.m-d.net. |
IPv4: HK
IPv6: US |
AS40138 - MDNET - Mach Dilemma, LLC, US
AS40138 - MDNET - Mach Dilemma, LLC, US |
| ns.m-d.net. | IPv4: US | AS15169 - GOOGLE - Google LLC, US |
| puck.nether.net. |
IPv4: US
IPv6: US |
AS2914 - NTT-COMMUNICATIONS-2914 - NTT America, Inc., US
AS2914 - NTT-COMMUNICATIONS-2914 - NTT America, Inc., US |
We detected the following errors or warnings about your DNS configuration. These caused your DNS rating to be lowered. Resolving these will grant a higher DNS Spy rating for your domain.
- No DNSSEC records found. Consider enabling DNSSEC, as it provides a way to validate DNS responses for data integrity.
We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.
- No CAA records found. Consider adding CAA records, as it adds increased security by limiting which Certificate Authorities can issue certificates for this domain. (more info)
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- You have more than 1 nameserver.
- The IPv4 nameservers are distributed among multiple providers.
- The IPv4 nameservers are distributed across multiple locations.
- The IPv6 nameservers are distributed among multiple providers.
- The IPv6 nameservers are distributed across multiple locations.
- The nameservers are being operated from multiple domains (m-d.net, nether.net).
DNS records: 100%
Our scans detected the following publicly available DNS records.
| Record | TTL | Value | |
|---|---|---|---|
| A | m-d.net | 24h | 107.170.226.83 |
| MX | m-d.net | 1h |
1 aspmx.l.google.com. 10 alt3.aspmx.l.google.com. 10 alt4.aspmx.l.google.com. 5 alt1.aspmx.l.google.com. 5 alt2.aspmx.l.google.com. |
| NS | m-d.net | 1h |
anyns1.m-d.net. anyns2.m-d.net. ns.m-d.net. puck.nether.net. |
| SOA | m-d.net | 24h | anyns1.m-d.net. hostmaster.m-d.net. 2019041104 28800 7200 864000 300 |
| TXT | m-d.net | 1h |
"google-site-verification=_ZntIJq8cp2wawDzhpAPCwjMMzJpFxmhQ2-6BKYeILE" "v=spf1 include:_spf.google.com ~all" |
| TXT | _dmarc.m-d.net | 1h | "v=DMARC1\; p=none\; rua=mailto:[email protected]" |
| A | anyns1.m-d.net | 24h | 45.127.112.20 |
| A | anyns2.m-d.net | 24h | 45.127.113.20 |
| CNAME | mail.m-d.net | 1h | ghs.googlehosted.com. |
| A | ns.m-d.net | 1h | 35.226.188.118 |
| A | www.m-d.net | 24h | 107.170.226.83 |
Good news, no warnings or errors were found.
We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.
- You have DMARC records configured, but the "p=none" policy only triggers reports to your e-mail address, the receiver is instructed to not take actions.
- No IPv6 record has been found on the zone apex (m-d.net). Consider enabling IPv6 in the infrastructure by adding an AAAA record on this domain.
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- Multiple MX records found.
- MX records with different priorities found (main + fall-back mailservers).
- The MX record for "m-d.net" has a long TTL (1h+).
- The MX records points to multiple mailservers.
- The NS records have a long TTL (1h+).
- Your SOA serial number follows the best practice YYYYMMDDxx format.
- SPF records have been found.
- SPF records are set up restrictively.
- DMARC records have been found.
- Found a root (apex) DNS record.
- Found a www DNS record.
- The active nameservers match the NS records.
- The DNS records appear to be RFC compliant.
Have a look at other public DNS scans.