weldom.fr

Checked 22 October 2026, 05:58 UTC · via 8.8.8.8
!Passed with warnings
27 passed 3 warnings 0 failed 4 info

Registration

info

.fr country-code · NAMESHIELD · expires 2027-02-22

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
NAMESHIELD
Registered
19 June 2008
Last changed
25 February 2026
Expires
22 February 2027
Status
client transfer prohibited
Registry nameservers
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, nsa.perf1.fr, nsb.perf1.com, nsc.perf1.com
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-02-22 #3
    The registration is valid until 2027-02-22 (123 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

pass

ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, nsa.perf1.fr, nsb.perf1.com, nsc.perf1.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, nsa.perf1.fr, nsb.perf1.com, nsc.perf1.com
NS in the zone
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, nsa.perf1.fr, nsb.perf1.com, nsc.perf1.com
NameserverAddressesNetwork (AS)Glue
ns-cloud-b1.googledomains.com216.239.32.107 2001:4860:4802:32::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud-b2.googledomains.com216.239.34.107 2001:4860:4802:34::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud-b3.googledomains.com216.239.36.107 2001:4860:4802:36::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud-b4.googledomains.com216.239.38.107 2001:4860:4802:38::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
nsa.perf1.fr81.92.94.100 2a01:c8:100::100AS20756 NAMESHIELD - NAMESHIELD SAS, FR AS20756 NAMESHIELD - NAMESHIELD SAS, FR81.92.94.100 2a01:c8:100::100
nsb.perf1.com81.92.95.100 2a01:c8:101::100AS20756 NAMESHIELD - NAMESHIELD SAS, FR AS20756 NAMESHIELD - NAMESHIELD SAS, FR-
nsc.perf1.com152.89.172.100 2a09:35c0:102::100AS209510 NAMESHIELDGRP - NAMESHIELD SAS, FR AS209510 NAMESHIELDGRP - NAMESHIELD SAS, FR-

Checks

  • ✓ 7 nameservers #6
    Delegated to ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, nsa.perf1.fr, nsb.perf1.com, nsc.perf1.com.
  • ✓ 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 7 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS15169 (GOOGLE - Google LLC, US): 8 addresses; AS20756 (NAMESHIELD - NAMESHIELD SAS, FR): 4 addresses; AS209510 (NAMESHIELDGRP - NAMESHIELD SAS, FR): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .fr.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

14 of 14 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-cloud-b1.googledomains.com 216.239.32.107NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud-b1.googledomains.com 2001:4860:4802:32::6bNOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud-b2.googledomains.com 216.239.34.107NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns-cloud-b2.googledomains.com 2001:4860:4802:34::6bNOERROR, 12 ms, authoritativenoyes / yesrefused-
ns-cloud-b3.googledomains.com 216.239.36.107NOERROR, 42 ms, authoritativenoyes / yesrefused-
ns-cloud-b3.googledomains.com 2001:4860:4802:36::6bNOERROR, 42 ms, authoritativenoyes / yesrefused-
ns-cloud-b4.googledomains.com 216.239.38.107NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns-cloud-b4.googledomains.com 2001:4860:4802:38::6bNOERROR, 13 ms, authoritativenoyes / yesrefused-
nsa.perf1.fr 81.92.94.100NOERROR, 4 ms, authoritativenoyes / yesrefusedSecure
nsa.perf1.fr 2a01:c8:100::100NOERROR, 4 ms, authoritativenoyes / yesrefusedSecure
nsb.perf1.com 81.92.95.100NOERROR, 10 ms, authoritativenoyes / yesrefusedSecure
nsb.perf1.com 2a01:c8:101::100NOERROR, 4 ms, authoritativenoyes / yesrefusedSecure
nsc.perf1.com 152.89.172.100NOERROR, 4 ms, authoritativenoyes / yesrefusedSecure
nsc.perf1.com 2a09:35c0:102::100NOERROR, 4 ms, authoritativenoyes / yesrefusedSecure

Checks

  • ✓ All respond #14
    All 14 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: nsa.perf1.fr: "Secure"; nsb.perf1.com: "Secure"; nsc.perf1.com: "Secure".
    #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

warn

serial 2025120914 · primary nsa.perf1.fr

Found

Primary (MNAME)
nsa.perf1.fr
Contact (RNAME)
technical.nameshield.net
Serial
2025120914
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns-cloud-b1.googledomains.com (216.239.32.107)2025120914
ns-cloud-b1.googledomains.com (2001:4860:4802:32::6b)2025120914
ns-cloud-b2.googledomains.com (216.239.34.107)2025120914
ns-cloud-b2.googledomains.com (2001:4860:4802:34::6b)2025120914
ns-cloud-b3.googledomains.com (216.239.36.107)2025120914
ns-cloud-b3.googledomains.com (2001:4860:4802:36::6b)2025120914
ns-cloud-b4.googledomains.com (216.239.38.107)2025120914
ns-cloud-b4.googledomains.com (2001:4860:4802:38::6b)2025120914
nsa.perf1.fr (81.92.94.100)2026101716
nsa.perf1.fr (2a01:c8:100::100)2026101716
nsb.perf1.com (81.92.95.100)2026101716
nsb.perf1.com (2a01:c8:101::100)2026101716
nsc.perf1.com (152.89.172.100)2026101716
nsc.perf1.com (2a09:35c0:102::100)2026101716

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2025120914 on ns-cloud-b1.googledomains.com (216.239.32.107), ns-cloud-b1.googledomains.com (2001:4860:4802:32::6b), ns-cloud-b2.googledomains.com (216.239.34.107), ns-cloud-b2.googledomains.com (2001:4860:4802:34::6b), ns-cloud-b3.googledomains.com (216.239.36.107), ns-cloud-b3.googledomains.com (2001:4860:4802:36::6b), ns-cloud-b4.googledomains.com (216.239.38.107), ns-cloud-b4.googledomains.com (2001:4860:4802:38::6b); 2026101716 on nsa.perf1.fr (81.92.94.100), nsa.perf1.fr (2a01:c8:100::100), nsb.perf1.com (81.92.95.100), nsb.perf1.com (2a01:c8:101::100), nsc.perf1.com (152.89.172.100), nsc.perf1.com (2a09:35c0:102::100). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver nsa.perf1.fr is one of the listed nameservers.
  • ✓ Contact technical@nameshield.net #25
    The SOA RNAME technical.nameshield.net means technical@nameshield.net.
  • ✓ Date-based serial #26
    The serial 2025120914 follows the YYYYMMDDnn convention (2025-12-09).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC3
NSEC3
1 iterations, 8-byte salt
Signatures valid until
9 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
60475KSK (257)ECDSAP256SHA256 (13)
31755ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-09 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-09 11:40 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 1 iteration and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

info

26 records at the apex

Found

Read from
216.239.32.107:53
TypeValueTTL
SOAnsa.perf1.fr. technical.nameshield.net. 2025120914 28800 7200 604800 720021600
NSnsb.perf1.com.86400
NSnsc.perf1.com.86400
NSnsa.perf1.fr.86400
NSns-cloud-b3.googledomains.com.86400
NSns-cloud-b4.googledomains.com.86400
NSns-cloud-b2.googledomains.com.86400
NSns-cloud-b1.googledomains.com.86400
A151.101.130.64300
MX10 mxa-004bb303.gslb.pphosted.com.3600
MX10 mxb-004bb303.gslb.pphosted.com.3600
TXT"figma-domain-verification=47e47ba19b3ce7e96f0addbd2d93881ded5c467a568d9a733ad8734bd60a2d83-1762264058"3600
TXT"google-site-verification=9lvz5GeSRPiGnXlY7rEVZHzIuNGL3WokjeKeVXmcTkM"3600
TXT"google-site-verification=WElbTc9we19ECfclbcnQBvEH7sGrmjMekC7YVOqApmM"3600
TXT"adobe-idp-site-verification=cc88d81147e75091a30a77d1d30d11039df985233af107344402ce50cd3e6790"3600
TXT"atlassian-domain-verification=TyaKvAX0UU8BlN1JKOirjNvpd7WXTpDQ6dGjItKHSqpsfaHAFsaQyazTgaCCvYZH"3600
TXT"brevo-code:99c3e419f061bf98b5214fbbab709972"3600
TXT"atlassian-domain-verification=QyOuzfNDro8hX8QBpdxuetS0NsV4vTpLwrmnbU5YGKkUlQKh23NipVlnpPPG0s1I"3600
TXT"google-site-verification=spDHURKptWrIlfCV22kiLNHMGeRIE1Xzfb6-Atkbpas"3600
TXT"facebook-domain-verification=akf71yep01x1ucvcyl1yz1otr3u0lr"3600
TXT"v=spf1 include:spf-004bb303.pphosted.com include:_spf.google.com include:spf_c.oraclecloud.com include:spf.mailjet.com ip4:213.245.2.3 ip4:213.245.2.36 ip4:213.245.2.35 ip4:213.245.2.33 ip4:185.92.37.57 ip4:31.172.232.198 -all"3600
TXT"docusign=7414eba3-5910-4c12-904b-f87e185671d2"3600
TXT"_globalsign-domain-verification=0PzXo4DngW04-DKmj0k_yzldOJIxclcPfSIXe2t_sZ"3600
TXT"google-site-verification=r89wS-90HVgOqZgllktfA1MU8Gvh-qfvVJgif1pus5U"3600
TXT"google-site-verification=PIKT30PBZEW6cXSf7n2Pv5rKhp61ki8aWe6-vU8lMzo"3600
TXT"miro-verification=135397bcb353186d419eb74fffc2b6adf6a5a62f"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, NS 1d. The NS TTL at the parent is 1h 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