culligan.fr

Checked 22 October 2026, 02:29 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 5 info

Registration

info

.fr country-code · CSC CORPORATE DOMAINS INC. · expires 2027-05-26

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
CSC CORPORATE DOMAINS INC.
Registered
21 June 1998
Last changed
27 May 2026
Expires
26 May 2027
Status
active
Registry nameservers
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
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-05-26 #3
    The registration is valid until 2027-05-26 (216 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

info

ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
NS in the zone
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-04.azure-dns.com13.107.236.4 2603:1061:0:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2-04.azure-dns.net150.171.21.4 2620:1ec:8ec:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-04.azure-dns.org204.14.183.4 2a01:111:4000:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-04.azure-dns.info208.84.5.4 2620:1ec:bda:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-04.azure-dns.com 13.107.236.4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1-04.azure-dns.com 2603:1061:0:700::4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 150.171.21.4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 2620:1ec:8ec:700::4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 204.14.183.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 2a01:111:4000:700::4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-04.azure-dns.info 208.84.5.4NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-04.azure-dns.info 2620:1ec:bda:700::4NOERROR, 5 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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: ns4-04.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #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

pass

serial 1 · primary ns1-04.azure-dns.com

Found

Primary (MNAME)
ns1-04.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-04.azure-dns.com (13.107.236.4)1
ns1-04.azure-dns.com (2603:1061:0:700::4)1
ns2-04.azure-dns.net (150.171.21.4)1
ns2-04.azure-dns.net (2620:1ec:8ec:700::4)1
ns3-04.azure-dns.org (204.14.183.4)1
ns3-04.azure-dns.org (2a01:111:4000:700::4)1
ns4-04.azure-dns.info (208.84.5.4)1
ns4-04.azure-dns.info (2620:1ec:bda:700::4)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-04.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

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

warn

20 records at the apex

Found

Read from
13.107.236.4:53
TypeValueTTL
SOAns1-04.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-04.azure-dns.com.172800
NSns2-04.azure-dns.net.172800
NSns3-04.azure-dns.org.172800
NSns4-04.azure-dns.info.172800
A20.234.37.1713600
MX10 mxb-00305802.gslb.pphosted.com.1
MX10 mxa-00305802.gslb.pphosted.com.1
TXT"v=spf1 IP4:37.71.155.61 include:spf.protection.outlook.com include:amazonses.com include:spf-00305802.pphosted.com include:spf.mailjet.com include:spf.mandrillapp.com include:aspmx.pardot.com include:eskerondemand.com include:spf.odmad.quest-on-demand.com" " -all"1
TXT"google-site-verification=yqWhCtlk9wKYLjl5VWWZixjRhvhfW5sWPTOIjGOjV3A"1
TXT"apple-domain-verification=3QGWVDn30y8FZavp"1
TXT"v=DMARC1; p=none; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com"1
TXT"pardot584793=bffa3acfb93b1328ad6b86d65ee8e4cb51585516420ea08fc532e1e198a32b8b"1
TXT"PrPJcnNjJR6AUKWjDpqe2hUow2pGjgqzkCR3AfHvDrE="1
TXT"4DSROK4K2NtD1qN60NZyPHwV2eB3pkguMjTFsmREoZ2oCD/8zqf6moJCFK37H7b59+/t0tgkAd4F3jJweoaBJA=="1
TXT"Da3fE4kQE+19mzcwigfUQfjpHwq8isSFHWcRktsUuN1uRM3re4AAQMRiTsqRm/HFHuxFkNwnSWb0AwuhTJ26iA=="1
TXT"MS=ms27830982"1
TXT"pardot1044463=135e25d407d82e964751a50987cb8fae6f959e82d329bcb7909bdcb159a2ff6d"1
TXT"sending_domain1044463=45323302aa87ae01956c5c9502e60389e4a8cbe7a8d3d5cfe3c37190fdc9511d"1
TXT"onetrust-domain-verification=e8833cc915094f3aa91df3bb223de1a2"1

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
    #32
  • ✓ 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