Domain report: communication-pro.fr

Registration

info

.fr country-code · OVH · expires 2027-08-22

TLD: .fr (country-code)
ICANN policies apply: no
Registrar: OVH
Registered: 22 August 2006
Last changed: 30 September 2026
Expires: 22 August 2027
Status: active
Registry nameservers: dns1.communication-pro.net, dns2.communication-pro.net
RDAP server: https://rdap.nic.fr/

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-08-22 #3

The registration is valid until 2027-08-22 (304 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.

warn

dns1.communication-pro.net, dns2.communication-pro.net

Nameserver	Addresses	Network (AS)	Glue
dns1.communication-pro.net	87.98.186.201	AS16276 OVH - OVH SAS, FR	-
dns2.communication-pro.net	87.98.162.190	AS16276 OVH - OVH SAS, FR	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.communication-pro.net, dns2.communication-pro.net.

#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 different networks #10

The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH 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 .net

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

fail

2 of 2 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns1.communication-pro.net 87.98.186.201	NOERROR, 15 ms, authoritative	no	no / yes	refused	PowerDNS Authoritative Server 4.0.3
dns2.communication-pro.net 87.98.162.190	NOERROR, 15 ms, authoritative	no	no / yes	refused	PowerDNS Authoritative Server 4.0.3

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

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.communication-pro.net: "PowerDNS Authoritative Server 4.0.3"; dns2.communication-pro.net: "PowerDNS Authoritative Server 4.0.3". Hide or replace the version string.

#17
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✗

No DNS over TCP

DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns1.communication-pro.net (87.98.186.201): dial tcp 87.98.186.201:53: i/o timeout; dns2.communication-pro.net (87.98.162.190): dial tcp 87.98.162.190:53: i/o timeout.

#19
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

pass

serial 2019072204 · primary dns1.communication-pro.net

Nameserver	Serial
dns1.communication-pro.net (87.98.186.201)	2019072204
dns2.communication-pro.net (87.98.162.190)	2019072204

✓ Serial 2019072204 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 8h, retry 2h, expire 7d, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver dns1.communication-pro.net is one of the listed nameservers.
✓ Contact mgiry@epixelic.com #25

The SOA RNAME mgiry.epixelic.com means mgiry@epixelic.com.
✓ Date-based serial #26

The serial 2019072204 follows the YYYYMMDDnn convention (2019-07-22).

warn

Not signed

info

7 records at the apex

Type	Value	TTL
SOA	dns1.communication-pro.net. mgiry.epixelic.com. 2019072204 28800 7200 604800 86400	3600
NS	dns1.communication-pro.net.	86400
NS	dns2.communication-pro.net.	86400
A	91.121.34.170	86400
MX	10 mx1.communication-pro.net.	86400
MX	50 mx2.communication-pro.net.	86400
TXT	"v=spf1 a mx ip4:51.254.1.14 ~all"	86400

✓ TTLs within range #32

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