Connectivity: 100%
The following nameservers are available and responding correctly for DNS queries for your domain logerenbijdeboswachter.nl.
Nameserver | IP address(es) | SOA serial |
---|---|---|
ns0.rijksoverheidnl.com. |
185.136.96.82
2a06:fb00:1::1:82 |
2024120305 |
ns1.rijksoverheidnl.nl. |
178.22.85.27
2a00:d00:3:6::130 |
2024120305 |
ns2.rijksoverheidnl.eu. |
94.228.142.136
2a00:d01:3:1::20 |
2024120305 |
ns3.rijksoverheidnl.org. |
145.100.177.67
2001:610:188:203:3:1:0:67 |
2024120305 |
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 |
---|---|---|
ns0.rijksoverheidnl.com. |
185.136.96.82
2a06:fb00:1::1:82 |
1ms
1ms |
ns1.rijksoverheidnl.nl. |
178.22.85.27
2a00:d00:3:6::130 |
1ms
1ms |
ns2.rijksoverheidnl.eu. |
94.228.142.136
2a00:d01:3:1::20 |
1ms
1ms |
ns3.rijksoverheidnl.org. |
145.100.177.67
2001:610:188:203:3:1:0:67 |
1ms
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 ns0.rijksoverheidnl.com. (185.136.96.82) replied quickly (< 50ms).
- Nameserver ns0.rijksoverheidnl.com. (2a06:fb00:1::1:82) replied in a reasonable time.
- Nameserver ns1.rijksoverheidnl.nl. (178.22.85.27) replied quickly (< 50ms).
- Nameserver ns1.rijksoverheidnl.nl. (2a00:d00:3:6::130) replied in a reasonable time.
- Nameserver ns2.rijksoverheidnl.eu. (94.228.142.136) replied quickly (< 50ms).
- Nameserver ns2.rijksoverheidnl.eu. (2a00:d01:3:1::20) replied in a reasonable time.
- Nameserver ns3.rijksoverheidnl.org. (145.100.177.67) replied quickly (< 50ms).
- Nameserver ns3.rijksoverheidnl.org. (2001:610:188:203:3:1:0:67) replied in a reasonable time.
Resilience & Security: 100%
These are the locations and providers of your nameservers.
Nameserver | Location | ISP |
---|---|---|
ns0.rijksoverheidnl.com. |
IPv4: BG
IPv6: BG |
AS203391 - CLOUDNSNET Cloud DNS Ltd., BG
AS203391 - CLOUDNSNET Cloud DNS Ltd., BG |
ns1.rijksoverheidnl.nl. |
IPv4: NL
IPv6: NL |
AS41887 - PROLOCATION Prolocation, NL
AS41887 - PROLOCATION Prolocation, NL |
ns2.rijksoverheidnl.eu. |
IPv4: NL
IPv6: NL |
AS41887 - PROLOCATION Prolocation, NL
AS41887 - PROLOCATION Prolocation, NL |
ns3.rijksoverheidnl.org. |
IPv4: NL
IPv6: NL |
AS1103 - SURFNET-NL SURFnet, The Netherlands, NL
AS1103 - SURFNET-NL SURFnet, The Netherlands, NL |
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.
- 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.
- DNSSEC is enabled.
- CAA records found.
- The nameservers are being operated from multiple domains (rijksoverheidnl.com, rijksoverheidnl.nl, rijksoverheidnl.eu, rijksoverheidnl.org).
DNS records: 93%
Our scans detected the following publicly available DNS records.
Record | TTL | Value | |
---|---|---|---|
A | logerenbijdeboswachter.nl | 3h | 93.119.0.181 |
AAAA | logerenbijdeboswachter.nl | 3h | 2a01:7c8:bb0a:65a::1 |
CAA | logerenbijdeboswachter.nl | 3h |
0 iodef "mailto:[email protected]" 0 issue "globalsign.com" 0 issue "letsencrypt.org" 0 issue "sectigo.com" 0 issuewild "sectigo.com" |
DNSKEY | logerenbijdeboswachter.nl | 24h | KSK | ECDSA Curve P-256 with SHA-256 | ioRowBguBUUV+VyXTnVz6afcw4ms5yVaFNcv8W/ZSr2bj1ISezjTjCwK 5e4fTIsDiRAfWypYIuVYzPsk2yfepA== |
MX | logerenbijdeboswachter.nl | 3h | 10 mail.logerenbijdeboswachter.nl. |
NS | logerenbijdeboswachter.nl | 3h |
ns0.rijksoverheidnl.com. ns1.rijksoverheidnl.nl. ns2.rijksoverheidnl.eu. ns3.rijksoverheidnl.org. |
SOA | logerenbijdeboswachter.nl | 3h | ns1.rijksoverheidnl.nl. domeinnaam.minaz.nl. 2024120305 10800 3600 604800 86400 |
TXT | logerenbijdeboswachter.nl | 3h | "v=spf1 include:spf.mandrillapp.com include:sparkpostmail.com ~all" |
CNAME | _dmarc.logerenbijdeboswachter.nl | 3h | sbb.reject.dmarc.mailpolicies.nl. |
TXT | api.logerenbijdeboswachter.nl | 3h | "v=spf1 -all" |
A | mail.logerenbijdeboswachter.nl | 3h | 83.160.58.101 |
CNAME | new.logerenbijdeboswachter.nl | 3h | files.logerenbijdeboswachter.nl. |
CNAME | www.logerenbijdeboswachter.nl | 3h | sbb-lb.amz.snkwr.net. |
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.
- We only detected 1 MX record. Multiple MX records (or multiple IPs behind the MX record) provide redundancy and a more robust e-mail setup.
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 DMARC records have been found. Consider configuring DMARC for improved e-mail authentication.
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- The MX record for "logerenbijdeboswachter.nl" has a long TTL (1h+).
- 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.
- Found a root (apex) DNS record.
- Found a www DNS record.
- Found an IPv6 root 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.