DNS Spy
Connectivity: 71%
The following nameservers are available and responding correctly for DNS queries for your domain wrcmn.org.
| Nameserver | IP address(es) | SOA serial |
|---|---|---|
| dns1msp.popp.net. | 208.254.148.69 | 97 |
| dns2msp.popp.net. | 208.254.148.100 | 97 |
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.
- The nameserver IPs are on the same /24 subnet.
- No IPv6 reachable nameservers were found. Users on IPv6-only networks are unable to reach you.
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.
- All nameservers are online.
- Nameservers are available over IPv4.
Performance: 100%
We tested each nameserver and measured the following response times.
| Nameserver | IP address(es) | Response time |
|---|---|---|
| dns1msp.popp.net. | 208.254.148.69 | 32ms |
| dns2msp.popp.net. | 208.254.148.100 | 1ms |
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.
- Nameserver dns1msp.popp.net. (208.254.148.69) replied quickly (< 50ms).
- Nameserver dns2msp.popp.net. (208.254.148.100) replied quickly (< 50ms).
Resilience & Security: 25%
These are the locations and providers of your nameservers.
| Nameserver | Location | ISP |
|---|---|---|
| dns1msp.popp.net. | IPv4: US | AS46303 - POPP-COM, US |
| dns2msp.popp.net. | IPv4: US | AS46303 - POPP-COM, 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.
- All IPv4 nameservers are hosted by the same provider (AS46303 - POPP-COM, US). Consider spreading the nameservers across multiple DNS providers for increased redundancy.
- No DNSSEC records found. Consider enabling DNSSEC, as it provides a way to validate DNS responses for data integrity.
- All the nameservers are being operated from a single domain (popp.net). If that domain gets compromised or goes offline, the DNS will be unavailable. Consider spreading the nameservers across multiple domains.
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.
- All IPv4 nameservers appear to be hosted in the same country (US). You might want to consider spreading the nameservers geographically.
- 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.
DNS records: 100%
Our scans detected the following publicly available DNS records.
| Record | TTL | Value | |
|---|---|---|---|
| A | wrcmn.org | 1h | 117.120.14.236 |
| MX | wrcmn.org | 1h |
10 mx1-us1.ppe-hosted.com. 20 mx2-us1.ppe-hosted.com. |
| NS | wrcmn.org | 1h |
dns1msp.popp.net. dns2msp.popp.net. |
| SOA | wrcmn.org | 1h | dns1msp.popp.net. hostmaster. 97 900 600 604800 3600 |
| TXT | wrcmn.org | 1h |
"MS=ms23541926" "google-site-verification=Whe-xUiOjvftdc7FYATjQDpmrqPrioPsaUJTiz0IZHI" "ppe-ec8fb4d56bd6dedda4a0" "v=spf1 mx a ip4:50.173.196.10 ip4:63.225.149.81 ip4:173.240.23.185 ip4:117.120.14.235 a:dispatch-us.ppe-hosted.com include:_spf.createsend.com include:spf.protection.outlook.com ~all" |
| TXT | _dmarc.wrcmn.org | 1h | "v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1:d:s" |
| SRV | _sip._tls.wrcmn.org | 1h | 100 1 443 sipdir.online.lync.com. |
| SRV | _sipfederationtls._tcp.wrcmn.org | 1h | 100 1 5061 sipfed.online.lync.com. |
| CNAME | autodiscover.wrcmn.org | 1h | autodiscover.outlook.com. |
| TXT | cm._domainkey.wrcmn.org | 1h | "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCq4IG1QbmWQ9SAvCSQExEMP+pf9MQhdUBd4ubWKRXqGGp9EYbB7YbqKrlKMpmDKoxe31wALIYbxhdoeHpdk/H3FWBxAyZwtLhaThCNLIswtsppL+688aXQjGSfBe2rvHeCu3BzZvf6u2yAluRgB/g8trTy+EZ8H7Uys9xq8ZJz3wIDAQAB" "" |
| CNAME | enterpriseenrollment.wrcmn.org | 1h | enterpriseenrollment.manage.microsoft.com. |
| CNAME | enterpriseregistration.wrcmn.org | 1h | enterpriseregistration.windows.net. |
| CNAME | lyncdiscover.wrcmn.org | 1h | webdir.online.lync.com. |
| A | mail.wrcmn.org | 1h | 50.173.196.11 |
| CNAME | msoid.wrcmn.org | 1h | clientconfig.microsoftonline-p.net. |
| A | new.wrcmn.org | 1h | 27.50.90.45 |
| A | remote.wrcmn.org | 1h | 50.173.196.13 |
| CNAME | selector1._domainkey.wrcmn.org | 1h | selector1-wrcmn-org._domainkey.wildliferehabilitation.onmicrosoft.com. |
| CNAME | selector2._domainkey.wrcmn.org | 1h | selector2-wrcmn-org._domainkey.wildliferehabilitation.onmicrosoft.com. |
| CNAME | sip.wrcmn.org | 1h | sipdir.online.lync.com. |
| A | vpn.wrcmn.org | 1h | 50.173.196.10 |
| CNAME | www.wrcmn.org | 1h | wrcmn.org. |
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 (wrcmn.org). 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 "wrcmn.org" has a long TTL (1h+).
- The MX records points to multiple mailservers.
- The NS records have a long TTL (1h+).
- 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.