erenumerique.fr

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

Registration

info

.fr country-code · SAFEBRANDS · expires 2027-04-29

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
SAFEBRANDS
Registered
24 August 2006
Last changed
11 December 2025
Expires
29 April 2027
Status
client delete prohibited
Registry nameservers
ns1pub.sfr.fr, ns2pub.sfr.fr
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-29 #3
    The registration is valid until 2027-04-29 (189 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: client delete prohibited). 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

ns1pub.sfr.fr, ns2pub.sfr.fr

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1pub.sfr.fr, ns2pub.sfr.fr
NS in the zone
ns1pub.sfr.fr, ns2pub.sfr.fr
NameserverAddressesNetwork (AS)Glue
ns1pub.sfr.fr92.90.26.129AS15557 LDCOMNET - Societe Francaise Du Radiotelephone - SFR SA, FR92.90.26.129
ns2pub.sfr.fr92.90.26.145AS15557 LDCOMNET - Societe Francaise Du Radiotelephone - SFR SA, FR92.90.26.145

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1pub.sfr.fr, ns2pub.sfr.fr.
    #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 92.90.26.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 (AS15557 (LDCOMNET - Societe Francaise Du Radiotelephone - SFR SA, 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 .fr
    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
ns1pub.sfr.fr 92.90.26.129NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2pub.sfr.fr 92.90.26.145NOERROR, 16 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

info

serial 35 · primary pranspub03.phys.prod

Found

Primary (MNAME)
pranspub03.phys.prod
Contact (RNAME)
support.dns.sfr.net
Serial
35
Refresh / retry
3600 s / 900 s
Expire
2419200 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1pub.sfr.fr (92.90.26.129)35
ns2pub.sfr.fr (92.90.26.145)35

Checks

  • ✓ Serial 35 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 28d, negative TTL 15m.
  • i
    Hidden master (not resolvable)
    The primary nameserver pranspub03.phys.prod is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact support@dns.sfr.net #25
    The SOA RNAME support.dns.sfr.net means support@dns.sfr.net.
  • ✓ Counter serial #26
    The serial 35 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
92.90.26.129:53
TypeValueTTL
SOApranspub03.phys.prod. support.dns.sfr.net. 35 3600 900 2419200 90028800
NSns2pub.sfr.fr.28800
NSns1pub.sfr.fr.28800
A109.24.47.21228800
MX0 smtp1.sfr.com.28800
MX20 erenumerique-fr.mail.protection.outlook.com.28800
MX10 smtp2.sfr.com.28800
TXT"MS=ms83326610"28800
TXT"MS=ms33754711"28800
TXT"MS=ms77888554"28800
TXT"v=spf1 ip4:188.165.172.7 ip4:77.154.154.200/30 ip4:77.154.156.200/30 include:_spf.google.com include:spf.protection.outlook.com include:aspmx.pardot.com ~all"28800
TXT"google-site-verification=TnPpyqh77jr-fe2ihfAGK2t6N9iMbJNa_M00aRU3tAI"28800
TXT"google-site-verification=CaHwjWm-qn-xaSB7h65W_--IjLgzslgefLfmUA1MVFk"28800

Checks

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