nfib.com

Checked 22 October 2026, 10:03 UTC · via 8.8.8.8
!Passed with warnings
26 passed 2 warnings 0 failed 3 info

Registration

info

.com generic · Network Solutions, LLC · expires 2027-12-15

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Network Solutions, LLC
Registered
9 March 1999
Last changed
16 October 2022
Expires
15 December 2027
Status
client transfer prohibited
Registry nameservers
ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-12-15 #3
    The registration is valid until 2027-12-15 (419 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info
NS in the zone
ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-07.azure-dns.com13.107.236.7 2603:1061:0:700::7AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US13.107.236.7 2603:1061:0:700::7
ns2-07.azure-dns.net150.171.21.7 2620:1ec:8ec:700::7AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-07.azure-dns.org204.14.183.7 2a01:111:4000:700::7AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-07.azure-dns.info208.84.5.7 2620:1ec:bda:700::7AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ 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
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-07.azure-dns.com 13.107.236.7NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-07.azure-dns.com 2603:1061:0:700::7NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-07.azure-dns.net 150.171.21.7NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-07.azure-dns.net 2620:1ec:8ec:700::7NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-07.azure-dns.org 204.14.183.7NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-07.azure-dns.org 2a01:111:4000:700::7NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-07.azure-dns.info 208.84.5.7NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-07.azure-dns.info 2620:1ec:bda:700::7NOERROR, 4 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-07.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #17
  • ✓ 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 20140507 · primary ns1-07.azure-dns.com

Found

Primary (MNAME)
ns1-07.azure-dns.com
Contact (RNAME)
hostmaster.nfib.org
Serial
20140507
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1-07.azure-dns.com (13.107.236.7)20140507
ns1-07.azure-dns.com (2603:1061:0:700::7)20140507
ns2-07.azure-dns.net (150.171.21.7)20140507
ns2-07.azure-dns.net (2620:1ec:8ec:700::7)20140507
ns3-07.azure-dns.org (204.14.183.7)20140507
ns3-07.azure-dns.org (2a01:111:4000:700::7)20140507
ns4-07.azure-dns.info (208.84.5.7)20140507
ns4-07.azure-dns.info (2620:1ec:bda:700::7)20140507

Checks

  • ✓ Serial 20140507 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-07.azure-dns.com is one of the listed nameservers.
  • ✓ Contact hostmaster@nfib.org #25
    The SOA RNAME hostmaster.nfib.org means hostmaster@nfib.org.
  • ✓ Counter serial #26
    The serial 20140507 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

15 records at the apex

Found

Read from
13.107.236.7:53
TypeValueTTL
SOAns1-07.azure-dns.com. hostmaster.nfib.org. 20140507 21600 3600 604800 86400500
NSns1-07.azure-dns.com.500
NSns2-07.azure-dns.net.500
NSns3-07.azure-dns.org.500
NSns4-07.azure-dns.info.500
A162.159.134.42500
MX0 nfib-com.mail.protection.outlook.com.3600
TXT"appsvc-nfibcom-redirect.azurewebsites.net"60
TXT"pardot_138571_*=d29bd8cd9b4a30858c46722957a118f8be6d9afe36532aec1318616df3c10c8a"60
TXT"MS=ms93872366"60
TXT"v=spf1 include:spf.protection.outlook.com include:relay.kinstamailservice.com -all"60
TXT"facebook-domain-verification=g2eapm4ooakbx8kobtwe46pwgpoaw2"60
TXT"cvl3drdoftclog37iemfteb4l6"60
TXT"7upe2jaakabmre3fa4o07gpbd7"60
TXT"ue56q438ccepspjgpgommogh7l"60

Checks

  • ✓ TTLs within range #32
    TTLs: A 8m20s, MX 1h, NS 8m20s. The NS TTL at the parent is 2d and in the zone 8m20s; 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