tempsdumonde.fr

Checked 22 October 2026, 05:24 UTC · via 8.8.8.8
✗Problems found
19 passed 3 warnings 3 failed 6 info

Registration

info

.fr country-code · BLOOM'UP · expires 2027-10-21

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
BLOOM'UP
Registered
21 October 2026
Last changed
21 October 2026
Expires
21 October 2027
Status
active, add period
Registry nameservers
ns01.bloomup.net, ns02.bloomup.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-10-21 #3
    The registration is valid until 2027-10-21 (364 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active, add period). 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

ns01.bloomup.net, ns02.bloomup.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns01.bloomup.net, ns02.bloomup.net
NS in the zone
ns01.bloomup.net, ns02.bloomup.net
NameserverAddressesNetwork (AS)Glue
ns01.bloomup.net51.75.201.160AS16276 OVH - OVH SAS, FR-
ns02.bloomup.net193.70.37.106AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.bloomup.net, ns02.bloomup.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 (AS16276 (OVH - OVH SAS, FR): 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

1 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.bloomup.net 51.75.201.160NOERROR, 16 ms, authoritativenoyes / yesALLOWED (7 records)9.18.49-1~deb12u2-Debian
ns02.bloomup.net 193.70.37.106REFUSED, 11 ms, NOT authoritativenono / yesrefused9.18.49-1~deb12u2-Debian

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns02.bloomup.net (193.70.37.106): REFUSED, authoritative=false.
    #15
  • ✓ 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: ns01.bloomup.net: "9.18.49-1~deb12u2-Debian"; ns02.bloomup.net: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns01.bloomup.net (51.75.201.160): 7 records. Restrict zone transfers to your secondary servers.
    #18
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns02.bloomup.net (193.70.37.106): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2025030204 · primary ns01.bloomup.net

Found

Primary (MNAME)
ns01.bloomup.net
Contact (RNAME)
support.bloomup.net
Serial
2025030204
Refresh / retry
14400 s / 7200 s
Expire
950400 s
Negative TTL
3600 s

Checks

  • ✓ Serial 2025030204 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 11d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.bloomup.net is one of the listed nameservers.
  • ✓ Contact support@bloomup.net #25
    The SOA RNAME support.bloomup.net means support@bloomup.net.
  • ✓ Date-based serial #26
    The serial 2025030204 follows the YYYYMMDDnn convention (2025-03-02).

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
51.75.201.160:53
TypeValueTTL
SOAns01.bloomup.net. support.bloomup.net. 2025030204 14400 7200 950400 36007200
NSns01.bloomup.net.3600
NSns02.bloomup.net.3600
A51.91.25.2393600
TXT"e755c8fba7167d499bdc7bcebfcdbf119ed31ed6"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, NS 1h.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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