ville-villiers-le-bel.fr

Checked 22 October 2026, 05:53 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 7 info

Registration

info

.fr country-code · BDL SYSTEMES dba Systonic · expires 2027-04-08

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
BDL SYSTEMES dba Systonic
Registered
24 February 1999
Last changed
31 May 2026
Expires
8 April 2027
Status
active
Registry nameservers
ns1.prodomaines.com, ns2.prodomaines.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-04-08 #3
    The registration is valid until 2027-04-08 (168 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). 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.prodomaines.com, ns2.prodomaines.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.prodomaines.com, ns2.prodomaines.com
NS in the zone
ns1.prodomaines.com, ns2.prodomaines.com
NameserverAddressesNetwork (AS)Glue
ns1.prodomaines.com193.169.64.191AS16347 INHERENT - ADISTA SAS, FR-
ns2.prodomaines.com193.169.64.192AS16347 INHERENT - ADISTA SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.prodomaines.com, ns2.prodomaines.com.
    #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 one network
    all IPv4 addresses are in 193.169.64.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16347 (INHERENT - ADISTA 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 .com
    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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.prodomaines.com 193.169.64.191NOERROR, 24 ms, authoritativenoyes / yesrefused-
ns2.prodomaines.com 193.169.64.192NOERROR, 23 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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

pass

serial 2026100803 · primary ns1.prodomaines.com

Found

Primary (MNAME)
ns1.prodomaines.com
Contact (RNAME)
dns-contact.systonic.fr
Serial
2026100803
Refresh / retry
86400 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.prodomaines.com (193.169.64.191)2026100803
ns2.prodomaines.com (193.169.64.192)2026100803

Checks

  • ✓ Serial 2026100803 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 30m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.prodomaines.com is one of the listed nameservers.
  • ✓ Contact dns-contact@systonic.fr #25
    The SOA RNAME dns-contact.systonic.fr means dns-contact@systonic.fr.
  • ✓ Date-based serial #26
    The serial 2026100803 follows the YYYYMMDDnn convention (2026-10-08).

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

15 records at the apex

Found

Read from
193.169.64.191:53
TypeValueTTL
SOAns1.prodomaines.com. dns-contact.systonic.fr. 2026100803 86400 1800 1209600 36003600
NSns1.prodomaines.com.3600
NSns2.prodomaines.com.3600
A57.130.68.123300
A57.130.68.125300
A57.130.68.124300
MX20 vade-mx-eu-fallback02.hornetsecurity.com.3600
MX20 vade-mx-eu-fallback01.hornetsecurity.com.3600
MX10 vade-mx-fr01.hornetsecurity.com.3600
MX10 vade-mx-fr02.hornetsecurity.com.3600
TXT"QuoVadis=3811fe5c-1194-41eb-98d2-8d59d12bd07c"3600
TXT"mandrill_verify.xs98D1iHtCjLWIGWcbb1AQ"3600
TXT"QuoVadis=bfe7a157-20fb-430e-acdc-ee198e2cabc4"3600
TXT"v=spf1 a:webmail.ville-villiers-le-bel.fr a:rmvsl.sigems.fr ip4:5.44.160.104 ip4:5.44.161.148 ip4:94.154.14.229 ip4:212.234.37.98 ip4:195.42.149.193 include:spf.cloud.vadesecure.com include:spf.mandrillapp.com include:spf.hornetsecurity.com -all"3600
TXT"MS=C8E97186DD90C2E2CFC64C868377774536EDD7B8"3600

Checks

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