invisionfree.com

Checked 22 October 2026, 09:21 UTC · via 8.8.8.8
✗Problems found
23 passed 1 warning 1 failed 6 info

Registration

info

.com generic · Tucows Domains Inc. · expires 2027-09-14

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Tucows Domains Inc.
Registered
14 September 2002
Last changed
18 September 2026
Expires
14 September 2027
Status
client transfer prohibited, client update prohibited
Registry nameservers
ns1.renewyourname.net, ns2.renewyourname.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-09-14 #3
    The registration is valid until 2027-09-14 (327 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

ns1.renewyourname.net, ns2.renewyourname.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.renewyourname.net, ns2.renewyourname.net
NS in the zone
ns1.renewyourname.net, ns2.renewyourname.net
NameserverAddressesNetwork (AS)Glue
ns1.renewyourname.net64.99.97.38 2604:4000:0:d:64:99:97:38AS15348 TUCOWS - Tucows.com Co., CA AS15348 TUCOWS - Tucows.com Co., CA-
ns2.renewyourname.net64.98.148.18 2604:4000:2800:d:64:99:148:18AS32491 TUCOWS-3 - Tucows.com Co., CA AS32491 TUCOWS-3 - Tucows.com Co., CA-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.renewyourname.net, ns2.renewyourname.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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15348 (TUCOWS - Tucows.com Co., CA): 2 addresses; AS32491 (TUCOWS-3 - Tucows.com Co., CA): 2 addresses.
  • 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

fail

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.renewyourname.net 64.99.97.38NOERROR, 98 ms, authoritativenoyes / yesrefusedparkeded-dns
ns1.renewyourname.net 2604:4000:0:d:64:99:97:38NOERROR, 95 ms, authoritativenoyes / yesrefusedparkeded-dns
ns2.renewyourname.net 64.98.148.18NOERROR, 120 ms, authoritativenono / yesrefusedparkeded-dns
ns2.renewyourname.net 2604:4000:2800:d:64:99:148:18NOERROR, 120 ms, authoritativenoyes / yesrefusedparkeded-dns

Checks

  • ✓ All respond #14
    All 4 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: ns1.renewyourname.net: "parkeded-dns"; ns2.renewyourname.net: "parkeded-dns".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns2.renewyourname.net (64.98.148.18): read tcp 46.225.38.91:32834->64.98.148.18:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026091804 · primary ns1.renewyourname.net

Found

Primary (MNAME)
ns1.renewyourname.net
Contact (RNAME)
hostmaster.renewyourname.net
Serial
2026091804
Refresh / retry
86400 s / 7200 s
Expire
2592000 s
Negative TTL
43200 s

Serial per nameserver

NameserverSerial
ns1.renewyourname.net (64.99.97.38)2026091804
ns1.renewyourname.net (2604:4000:0:d:64:99:97:38)2026091804
ns2.renewyourname.net (64.98.148.18)2026091804
ns2.renewyourname.net (2604:4000:2800:d:64:99:148:18)2026091804

Checks

  • ✓ Serial 2026091804 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 30d, negative TTL 12h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.renewyourname.net is one of the listed nameservers.
  • ✓ Contact hostmaster@renewyourname.net #25
    The SOA RNAME hostmaster.renewyourname.net means hostmaster@renewyourname.net.
  • ✓ Date-based serial #26
    The serial 2026091804 follows the YYYYMMDDnn convention (2026-09-18).

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

4 records at the apex

Found

Read from
64.99.97.38:53
TypeValueTTL
SOAns1.renewyourname.net. hostmaster.renewyourname.net. 2026091804 86400 7200 2592000 4320086400
NSns2.renewyourname.net.86400
NSns1.renewyourname.net.86400
A52.223.13.4186400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, 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.
  • 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