nationaljournal.com

Checked 22 October 2026, 10:00 UTC · via 8.8.8.8
!Passed with warnings
27 passed 1 warning 0 failed 3 info

Registration

info

.com generic · Network Solutions, LLC · expires 2029-01-23

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Network Solutions, LLC
Registered
22 January 1996
Last changed
30 April 2021
Expires
23 January 2029
Status
client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited
Registry nameservers
ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.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 2029-01-23 #3
    The registration is valid until 2029-01-23 (823 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

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

Found

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

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.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

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-01.azure-dns.com 13.107.236.1NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1-01.azure-dns.com 2603:1061:0:700::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-01.azure-dns.net 150.171.21.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-01.azure-dns.net 2620:1ec:8ec:700::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-01.azure-dns.org 204.14.183.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-01.azure-dns.org 2a01:111:4000:700::1NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-01.azure-dns.info 208.84.5.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-01.azure-dns.info 2620:1ec:bda:700::1NOERROR, 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 2019092216 · primary ns1-01.azure-dns.com

Found

Primary (MNAME)
ns1-01.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
2019092216
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-01.azure-dns.com (13.107.236.1)2019092216
ns1-01.azure-dns.com (2603:1061:0:700::1)2019092216
ns2-01.azure-dns.net (150.171.21.1)2019092216
ns2-01.azure-dns.net (2620:1ec:8ec:700::1)2019092216
ns3-01.azure-dns.org (204.14.183.1)2019092216
ns3-01.azure-dns.org (2a01:111:4000:700::1)2019092216
ns4-01.azure-dns.info (208.84.5.1)2019092216
ns4-01.azure-dns.info (2620:1ec:bda:700::1)2019092216

Checks

  • ✓ Serial 2019092216 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-01.azure-dns.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.
  • ✓ Date-based serial #26
    The serial 2019092216 follows the YYYYMMDDnn convention (2019-09-22).

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

22 records at the apex

Found

Read from
13.107.236.1:53
TypeValueTTL
SOAns1-01.azure-dns.com. azuredns-hostmaster.microsoft.com. 2019092216 3600 300 2419200 3003600
NSns1-01.azure-dns.com.86400
NSns2-01.azure-dns.net.86400
NSns3-01.azure-dns.org.86400
NSns4-01.azure-dns.info.86400
A150.171.109.1003600
MX10 alt4.aspmx.l.google.com.3600
MX10 alt3.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX1 aspmx.l.google.com.3600
TXT"v=spf1 include:49867955.spf02.hubspotemail.net include:_spf.mailgun.org include:_spf.salesforce.com include:_spf.google.com ~all"300
TXT"adobe-idp-site-verification=8b638b8d-0438-420a-947c-52cfdb90b351"300
TXT"google-site-verification=R0zWrL_2A5gx8GnjDdHwr_zoEqKKjPCPRYUU814Tgww"300
TXT"facebook-domain-verification=89re7e70wucbjnsy50cni8k1n7cksh"300
TXT"_globalsign-domain-verification=R1bvWDvJUF1gpXlmc7Q3deFwpZciil5dpJR4t-a8XM"300
TXT"google-site-verification=U0HqzcVbldD1YyG0uebJQafkHzlDBtqLK396RsProuU"300
TXT"google-site-verification=K0fvDmhGHpooF96lk9Wxapl1V1dgrA2x-TNb_yNe7hI"300
TXT"MS=ms73638501"300
TXT"google-site-verification=fr3IRIRu0tF8cgpf6QcviPzbpp8Y61zn1FscZuasZ8Q"300
TXT"google-site-verification=wyASePHNFvd2z7cX1TTtBPGryFCGqw0pY448XA7Zsd0"300
TXT"have-i-been-pwned-verification=dweb_zqz47psnxyzv9wrjz8z784nm"300

Checks

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