trib.com

Checked 22 October 2026, 11:12 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 8 info

Registration

info

.com generic · Tucows Domains Inc. · expires 2026-11-22

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Tucows Domains Inc.
Registered
23 November 1993
Last changed
23 October 2025
Expires
22 November 2026
Status
active
Registry nameservers
dns1.tn-cloud.net, dns2.tn-cloud.net
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 2026-11-22 #3
    The registration is valid until 2026-11-22 (30 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns1.tn-cloud.net, dns2.tn-cloud.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.tn-cloud.net, dns2.tn-cloud.net
NS in the zone
dns1.tn-cloud.net, dns2.tn-cloud.net
NameserverAddressesNetwork (AS)Glue
dns1.tn-cloud.net192.104.182.104AS10668 LEE-ASN - Lee Enterprises, Incorporated, US-
dns2.tn-cloud.net192.104.183.104AS10668 LEE-ASN - Lee Enterprises, Incorporated, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.tn-cloud.net, dns2.tn-cloud.net.
    #6
  • ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS10668 (LEE-ASN - Lee Enterprises, Incorporated, US): 2 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 .net
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.tn-cloud.net 192.104.182.104NOERROR, 104 ms, authoritativenoyes / yesrefusedDNS Server
dns2.tn-cloud.net 192.104.183.104NOERROR, 87 ms, authoritativenoyes / yesrefusedDNS Server

Checks

  • ✓ All respond #14
    All 2 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns1.tn-cloud.net: "DNS Server"; dns2.tn-cloud.net: "DNS Server".
    #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 1785870682 · primary dns1.tn-cloud.net

Found

Primary (MNAME)
dns1.tn-cloud.net
Contact (RNAME)
list_dnsadmin.tn-cloud.net
Serial
1785870682
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
dns1.tn-cloud.net (192.104.182.104)1785870682
dns2.tn-cloud.net (192.104.183.104)1785870682

Checks

  • ✓ Serial 1785870682 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.tn-cloud.net is one of the listed nameservers.
  • ✓ Contact list_dnsadmin@tn-cloud.net #25
    The SOA RNAME list_dnsadmin.tn-cloud.net means list_dnsadmin@tn-cloud.net.
  • ✓ Timestamp serial #26
    The serial 1785870682 is a Unix timestamp (2026-08-04 19:11 UTC).

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
192.104.182.104:53
TypeValueTTL
SOAdns1.tn-cloud.net. list_dnsadmin.tn-cloud.net. 1785870682 3600 300 2419200 72007200
NSdns1.tn-cloud.net.7200
NSdns2.tn-cloud.net.7200
A192.104.182.2097200
A192.104.182.1097200
MX20 mx0a-00292f01.pphosted.com.300
MX10 mx0b-00292f01.pphosted.com.300
TXT"ANWeyjBXTMPFQfCuqAvbahBmTLdKs25tYp1nBxRfzG1SAvP1HELePoL9mediwBtg//BwM1Xh+q/x4z5YFLDi/w=="7200
TXT"n2c3ddfc3naeafmlhktpqkluls"7200
TXT"adobe-idp-site-verification=039adc5854d3e2024125d174b988acafb7b42ea4a6c3fcc348d938dbd0b7f7ff"7200
TXT"facebook-domain-verification=6htuzsrm4wv4igxm7jcn0h0buzsikk"7200
TXT"v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:tn-cloud.net ~all"7200
TXT"MS=ms38155597"7200
TXT"knowbe4-site-verification=4d74bbd68c11b993425e4dcc4cf20593"7200
TXT"tollbit-domain-verification=c62e2c46868743c73cfc9afbdc9049b896ab02ae9548375bf6b0b8d10a4c8628"7200

Checks

  • ✓ TTLs within range #32
    TTLs: A 2h, MX 5m, NS 2h. The NS TTL at the parent is 2d and in the zone 2h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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