irss.fr

Checked 22 October 2026, 03:32 UTC · via 8.8.8.8
!Passed with warnings
26 passed 1 warning 0 failed 4 info

Registration

info

.fr country-code · GANDI · expires 2027-01-03

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
GANDI
Registered
6 February 2001
Last changed
15 December 2025
Expires
3 January 2027
Status
client transfer prohibited
Registry nameservers
ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.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-01-03 #3
    The registration is valid until 2027-01-03 (73 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

info

ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com
NS in the zone
ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com
NameserverAddressesNetwork (AS)Glue
ns1.bdm.microsoftonline.com13.107.236.208 2603:1061:0:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2.bdm.microsoftonline.com150.171.21.208 2620:1ec:8ec:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3.bdm.microsoftonline.com204.14.183.208 2a01:111:4000:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4.bdm.microsoftonline.com208.84.5.208 2620:1ec:bda:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.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 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
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.bdm.microsoftonline.com 13.107.236.208NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.bdm.microsoftonline.com 2603:1061:0:700::d0NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.bdm.microsoftonline.com 150.171.21.208NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.bdm.microsoftonline.com 2620:1ec:8ec:700::d0NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3.bdm.microsoftonline.com 204.14.183.208NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3.bdm.microsoftonline.com 2a01:111:4000:700::d0NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4.bdm.microsoftonline.com 208.84.5.208NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4.bdm.microsoftonline.com 2620:1ec:bda:700::d0NOERROR, 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.
  • ✓ 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 1 · primary ns1.bdm.microsoftonline.com

Found

Primary (MNAME)
ns1.bdm.microsoftonline.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.bdm.microsoftonline.com (13.107.236.208)1
ns1.bdm.microsoftonline.com (2603:1061:0:700::d0)1
ns2.bdm.microsoftonline.com (150.171.21.208)1
ns2.bdm.microsoftonline.com (2620:1ec:8ec:700::d0)1
ns3.bdm.microsoftonline.com (204.14.183.208)1
ns3.bdm.microsoftonline.com (2a01:111:4000:700::d0)1
ns4.bdm.microsoftonline.com (208.84.5.208)1
ns4.bdm.microsoftonline.com (2620:1ec:bda:700::d0)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.bdm.microsoftonline.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

info

13 records at the apex

Found

Read from
13.107.236.208:53
TypeValueTTL
SOAns1.bdm.microsoftonline.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1.bdm.microsoftonline.com.172800
NSns2.bdm.microsoftonline.com.172800
NSns3.bdm.microsoftonline.com.172800
NSns4.bdm.microsoftonline.com.172800
A185.31.41.1071800
AAAA2a00:b6e0:1:200:8::13600
MX0 irss-fr.mail.protection.outlook.com.3600
TXT"mscid=MQntPJ40mRH+i6fA8VQFns+94cmHSOczU7yiIMBzCjiElxoagsPHjkZixbZ/Ig9T8Sar+QFPfYFy+16wB+n8cg=="1800
TXT"MS=ms99174374"1800
TXT"google-site-verification=iSOgheQVNG_SO4N1ztX46r86RZ5OflCl-UDJyRfWyNU"1800
TXT"v=spf1 include:spf.protection.outlook.com -all"1800
TXT"google-site-verification=doF1cKkkeNfjbdIQEouZViVQOFZ6v-WcPajV2LVTBOg"1800

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, AAAA 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