impakt.nl

Checked 22 October 2026, 13:52 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 6 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/impakt.nl returned HTTP 429

Checks

  • i
    .nl is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .nl is delegated in the root zone and DNSSEC-signed.
  • i
    Could not be checked
    The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/impakt.nl returned HTTP 429
    #3

Delegation

warn

ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com
NS in the zone
ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com
NameserverAddressesNetwork (AS)Glue
ns1.bdm.microsoftonline.com13.107.236.208 2603:1061:0:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2.bdm.microsoftonline.com150.171.21.208 2620:1ec:8ec:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3.bdm.microsoftonline.com (zone only)204.14.183.208 2a01:111:4000:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4.bdm.microsoftonline.com (zone only)208.84.5.208 2620:1ec:bda:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com. ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com report NS ns1.bdm.microsoftonline.com ns2.bdm.microsoftonline.com ns3.bdm.microsoftonline.com ns4.bdm.microsoftonline.com.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.bdm.microsoftonline.com 13.107.236.208NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1.bdm.microsoftonline.com 2603:1061:0:700::d0NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.bdm.microsoftonline.com 150.171.21.208NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.bdm.microsoftonline.com 2620:1ec:8ec:700::d0NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3.bdm.microsoftonline.com 204.14.183.208NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3.bdm.microsoftonline.com 2a01:111:4000:700::d0NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4.bdm.microsoftonline.com 208.84.5.208NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4.bdm.microsoftonline.com 2620:1ec:bda:700::d0NOERROR, 5 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1 · primary ns1.bdm.microsoftonline.com

Found

Primary (MNAME)
ns1.bdm.microsoftonline.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.bdm.microsoftonline.com (13.107.236.208)1
ns1.bdm.microsoftonline.com (2603:1061:0:700::d0)1
ns2.bdm.microsoftonline.com (150.171.21.208)1
ns2.bdm.microsoftonline.com (2620:1ec:8ec:700::d0)1
ns3.bdm.microsoftonline.com (204.14.183.208)1
ns3.bdm.microsoftonline.com (2a01:111:4000:700::d0)1
ns4.bdm.microsoftonline.com (208.84.5.208)1
ns4.bdm.microsoftonline.com (2620:1ec:bda:700::d0)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.bdm.microsoftonline.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

11 records at the apex

Found

Read from
13.107.236.208:53
TypeValueTTL
SOAns1.bdm.microsoftonline.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1.bdm.microsoftonline.com.172800
NSns2.bdm.microsoftonline.com.172800
NSns3.bdm.microsoftonline.com.172800
NSns4.bdm.microsoftonline.com.172800
A35.214.176.43600
MX0 impakt-nl.mail.protection.outlook.com.3600
TXT"mscid=a/92DsQjpTL7ZTro2RKcungR3zPLJP3n3biO7X89/i/j4RXV8671aWoPri9y7SgcAMHFOyQr4V9hy//VUOZteA=="3600
TXT"v=spf1 ip4:195.211.74.36 include:spf.protection.outlook.com include:servers.mcsv.net include:sendgrid.net -all"3600
TXT"google-site-verification=OrbfvCNF42RbtcebAN43ZrmvVqe-T_cIsKFiiCpRzvo"3600
TXT"sendinblue-code:33c65297dc98e99b6736f806302f3ef1"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 2d. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35