tripod.fr

Checked 22 October 2026, 05:31 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 1 failed 7 info

Registration

info

.fr country-code · Virtualia LLC · expires 2027-09-11

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
Virtualia LLC
Registered
11 September 2026
Last changed
16 October 2026
Expires
11 September 2027
Status
pending transfer
Registry nameservers
ns1.park-my-domain.net, ns2.park-my-domain.net
RDAP server
https://rdap.nic.fr/

Checks

  • i
    .fr is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .fr is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-09-11 #3
    The registration is valid until 2027-09-11 (324 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: pending transfer). 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

ns1.park-my-domain.net, ns2.park-my-domain.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.park-my-domain.net, ns2.park-my-domain.net
NS in the zone
ns1.park-my-domain.net, ns2.park-my-domain.net
NameserverAddressesNetwork (AS)Glue
ns1.park-my-domain.net46.224.16.22AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.park-my-domain.net65.108.243.18AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.park-my-domain.net, ns2.park-my-domain.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 (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 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

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.park-my-domain.net 46.224.16.22NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.0 (built Oct 23 2025 15:53:21 by root@ns1.roller.ad)
ns2.park-my-domain.net 65.108.243.18NOERROR, 24 ms, authoritativenono / yesrefusedPowerDNS Authoritative Server 5.0.1 (built Nov 6 2025 13:41:20 by root@ns2.roller.ad)

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.park-my-domain.net: "PowerDNS Authoritative Server 5.0.0 (built Oct 23 2025 15:53:21 by root@ns1.roller.ad)"; ns2.park-my-domain.net: "PowerDNS Authoritative Server 5.0.1 (built Nov 6 2025 13:41:20 by root@ns2.roller.ad)". Hide or replace the version string.
    #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.park-my-domain.net (65.108.243.18): read tcp 46.225.38.91:39198->65.108.243.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 2026091107 · primary ns1.park-my-domain.net

Found

Primary (MNAME)
ns1.park-my-domain.net
Contact (RNAME)
hostmaster.tripod.fr
Serial
2026091107
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.park-my-domain.net (46.224.16.22)2026091107
ns2.park-my-domain.net (65.108.243.18)2026091107

Checks

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

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

5 records at the apex

Found

Read from
46.224.16.22:53
TypeValueTTL
SOAns1.park-my-domain.net. hostmaster.tripod.fr. 2026091107 7200 900 1209600 864001800
NSns2.park-my-domain.net.3600
NSns1.park-my-domain.net.3600
A157.90.33.74300
A157.90.33.73300

Checks

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