u-net.com

Checked 22 October 2026, 11:14 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 5 info

Registration

info

.com generic · Tucows Domains Inc. · expires 2027-08-23

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Tucows Domains Inc.
Registered
24 August 1994
Last changed
25 July 2026
Expires
23 August 2027
Status
client transfer prohibited, client update prohibited
Registry nameservers
ns0.clara.net, ns1.clara.net, ns2.clara.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 2027-08-23 #3
    The registration is valid until 2027-08-23 (304 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns0.clara.net, ns1.clara.net, ns2.clara.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns0.clara.net, ns1.clara.net, ns2.clara.net
NS in the zone
ns0.clara.net, ns1.clara.net, ns2.clara.net
NameserverAddressesNetwork (AS)Glue
ns0.clara.net185.77.72.10 2001:67c:1088::10AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns1.clara.net185.77.72.11 2001:67c:1088::11AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns2.clara.net195.245.201.35 2001:a88:0:fffa::3AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns0.clara.net, ns1.clara.net, ns2.clara.net.
  • ✓ 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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8426 (CLARANET-AS - Claranet Limited, GB): 6 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.clara.net 185.77.72.10NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns0.clara.net 2001:67c:1088::10NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.clara.net 185.77.72.11NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.clara.net 2001:67c:1088::11NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.clara.net 195.245.201.35NOERROR, 6 ms, authoritativenoyes / yesrefused-
ns2.clara.net 2001:a88:0:fffa::3NOERROR, 5 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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

warn

serial 2015021917 · primary ns0.clara.net

Found

Primary (MNAME)
ns0.clara.net
Contact (RNAME)
hostmaster.clara.net
Serial
2015021917
Refresh / retry
1200 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns0.clara.net (185.77.72.10)2015021917
ns0.clara.net (2001:67c:1088::10)2015021917
ns1.clara.net (185.77.72.11)2015021917
ns1.clara.net (2001:67c:1088::11)2015021917
ns2.clara.net (195.245.201.35)2015021917
ns2.clara.net (2001:a88:0:fffa::3)2015021917

Checks

  • ✓ Serial 2015021917 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 20m. Current values: refresh 20m, retry 1h, expire 7d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0.clara.net is one of the listed nameservers.
  • ✓ Contact hostmaster@clara.net #25
    The SOA RNAME hostmaster.clara.net means hostmaster@clara.net.
  • ✓ Date-based serial #26
    The serial 2015021917 follows the YYYYMMDDnn convention (2015-02-19).

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

7 records at the apex

Found

Read from
185.77.72.10:53
TypeValueTTL
SOAns0.clara.net. hostmaster.clara.net. 2015021917 1200 3600 604800 86400300
NSns1.clara.net.300
NSns2.clara.net.300
NSns0.clara.net.300
MX20 mx-vh.uk.vianw.net.300
MX10 vip-mx-vianw.mail.eu.clara.net.300
TXT"v=spf1 include:spf-claramail.mail.eu.clara.net ~all"900

Checks

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