kitco.com

Checked 22 October 2026, 09:32 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 2031-08-14

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Network Solutions, LLC
Registered
15 August 1995
Last changed
4 April 2023
Expires
14 August 2031
Status
client transfer prohibited
Registry nameservers
ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.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 2031-08-14 #3
    The registration is valid until 2031-08-14 (1756 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-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info

Found

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

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.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-03.azure-dns.com 13.107.236.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-03.azure-dns.com 2603:1061:0:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 150.171.21.3NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 2620:1ec:8ec:700::3NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 204.14.183.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 2a01:111:4000:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-03.azure-dns.info 208.84.5.3NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-03.azure-dns.info 2620:1ec:bda:700::3NOERROR, 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-03.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 2026070801 · primary ns1-03.azure-dns.com

Found

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

Serial per nameserver

NameserverSerial
ns1-03.azure-dns.com (13.107.236.3)2026070801
ns1-03.azure-dns.com (2603:1061:0:700::3)2026070801
ns2-03.azure-dns.net (150.171.21.3)2026070801
ns2-03.azure-dns.net (2620:1ec:8ec:700::3)2026070801
ns3-03.azure-dns.org (204.14.183.3)2026070801
ns3-03.azure-dns.org (2a01:111:4000:700::3)2026070801
ns4-03.azure-dns.info (208.84.5.3)2026070801
ns4-03.azure-dns.info (2620:1ec:bda:700::3)2026070801

Checks

  • ✓ Serial 2026070801 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-03.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 2026070801 follows the YYYYMMDDnn convention (2026-07-08).

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

25 records at the apex

Found

Read from
13.107.236.3:53
TypeValueTTL
SOAns1-03.azure-dns.com. azuredns-hostmaster.microsoft.com. 2026070801 3600 300 2419200 3003600
NSns1-03.azure-dns.com.86400
NSns2-03.azure-dns.net.86400
NSns3-03.azure-dns.org.86400
NSns4-03.azure-dns.info.86400
A34.36.185.491800
MX0 kitco-com.mail.protection.outlook.com.1800
TXT"v=spf1 mx include:_spf.ultipro.com include:spf.zoho.com include:transmail.net include:spf.protection.outlook.com include:spf.ca-1.a.mimecastprotect.com -all"1800
TXT"_globalsign-domain-verification=kfMq-Xsq8rng3kmcygtA5qy0W_fjUBd1dyg5KY2ZlA"1800
TXT"VGnarliGlKW1KAJ1QpubnTxcKWZIWQqb6tE1iBvhNJOXcMMpM7UZSR0df1HUkajxvqkvhwLUpUeIi2UdnS466w=="1800
TXT"kaz-mtl1-kitco-com-redirect.azurewebsites.net"1800
TXT"google-site-verification=9f6Mo6ZW-IcS3nxtIOvjhv4zIywYKnC8L-YaoYjULAQ"1800
TXT"MS=ms33623696"1800
TXT"fastly-domain-delegation-a3gxsjpaqpinhejpisao-726976-2023-12-22"1800
TXT"da5490964u82i1lccaupfqrb4m"1800
TXT"5qjgg7klmkhnr7sc54iscm88g2"1800
TXT"openai-domain-verification=dv-XNiD29ViA54D6DIgOHTHfhbS"1800
TXT"google-site-verification=-mif1IHNRTkBiZPGJHkt0-7QWLbC0l3ijcap2udldRI"1800
TXT"se9cbthjb2acj15jqs1059u1et"1800
TXT"ehcqu2mvgio1qn3b2of8j9fjht"1800
TXT"ktchv725hobnr9bbomob2bm1g5"1800
TXT"google-site-verification=NhuGxUohMCeBPovpocjT3tYlygDoAUct3xREH1Vo9Ao"1800
TXT"google-site-verification=b4Q7dptDjXJlIxl2VhpCDg5QQGFZsA9H91pu3-R05-I"1800
TXT"d365mktkey=kiPAG20tbg0zWOoXJnt4xmsxoRk0Qm6szUFlR8pC1IUx"1800
TXT"apple-domain-verification=72ZngQP4Bc8T9a9Y"1800

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, MX 30m, 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