audika.fr

Checked 22 October 2026, 01:50 UTC · via 8.8.8.8
✗Problems found
27 passed 2 warnings 1 failed 5 info

Registration

fail

.fr country-code · Abion AB · expires 2026-11-03

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
Abion AB
Registered
9 January 2000
Last changed
31 December 2025
Expires
3 November 2026
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 in 12 days
    The registration expires on 2026-11-03. Renew it now or enable auto-renewal.
    #3
  • 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, 4 ms, authoritativenoyes / yesrefused-
ns1-04.azure-dns.com 2603:1061:0:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 150.171.21.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 2620:1ec:8ec:700::4NOERROR, 4 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, 4 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, 4 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

warn

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

Found

Primary (MNAME)
ns1-04.azure-dns.com
Contact (RNAME)
dnsmaster.demant.com
Serial
31
Refresh / retry
900 s / 600 s
Expire
86400 s
Negative TTL
3600 s

Serial per nameserver

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

Checks

  • ✓ Serial 31 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 15m, retry 10m, expire 1d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-04.azure-dns.com is one of the listed nameservers.
  • ✓ Contact dnsmaster@demant.com #25
    The SOA RNAME dnsmaster.demant.com means dnsmaster@demant.com.
  • ✓ Counter serial #26
    The serial 31 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
23 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
44993ECDSAP256SHA256 (13)SHA256 9B6118F666E4AF20…yes

DNSKEY in the zone

Key tagRoleAlgorithm
44993KSK (257)ECDSAP256SHA256 (13)
27306ZSK (256)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 44993 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 00:49 UTC and expires at 2026-10-23 02:49 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

19 records at the apex

Found

Read from
13.107.236.4:53
TypeValueTTL
SOAns1-04.azure-dns.com. dnsmaster.demant.com. 31 900 600 86400 36003600
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.103.145.2073600
MX0 audika-fr.mail.protection.outlook.com.3600
TXT"workplace-domain-verification=rjZadnmzntpTVUkhOYyleu0IPoxRA4"3600
TXT"MS=ms13880747"3600
TXT"Ttj6aTVrHXF9pMpWSMbdk6G4Ae9n9a8mR4nBowwUj3Ny1yAP2b7NfWxfrVgZG2MEBcXDB+XR+mVD/YI1X04ZrA=="3600
TXT"v=spf1 a:mailout.demant.com include:spf.protection.outlook.com include:spf.sendinblue.com ip4:146.59.138.164 -all"3600
TXT"facebook-domain-verification=i03afg0qvoa0jwg08jgwghqyo5v2od"3600
TXT"apple-domain-verification=4OkBG4MVEjFdCLhC"3600
TXT"google-site-verification=WXEpp-4eRhkB5nlFRVUIdLOrCoi6o-UqPu_gX-85UQU"3600
TXT"google-site-verification=YaNHS0PT-AY3nste3UNJHKqfwzk_ADAYariw8zBgytc"3600
TXT"sendinblue-code:50756154ed629861ca00b30c127f73d6"3600
TXT"wombat-verification=3KwxVCQV1HEp-aRXRTKKaZ5G0frhk"3600
TXT"klaviyo-site-verification=WzQ2ix"3600
TXT"r0wwgBRB3E0Z8uoiLEsgAA"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 2d. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
  • ✓ 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