primebonus.fr

ns1.impreza.host, ns2.impreza.host, ns3.impreza.host, ns4.impreza.host

Found

Parent zone

fr

Delegation from

d.nic.fr (194.0.9.1)

NS at the parent

ns1.impreza.host, ns2.impreza.host, ns3.impreza.host, ns4.impreza.host

Checks

• ✓ 4 nameservers #6

  Delegated to ns1.impreza.host, ns2.impreza.host, ns3.impreza.host, ns4.impreza.host.
• ✓ 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 162.251.82.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 (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 16 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 .host

  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

16 of 16 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 16 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: ns1.impreza.host: "2026.10.8"; ns2.impreza.host: "2026.10.8"; ns3.impreza.host: "2026.10.8"; ns4.impreza.host: "2026.10.8". 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.

serial 1792644497 · primary 208.91.197.91

Found

Primary (MNAME)

208.91.197.91

Contact (RNAME)

hostmaster.primebonus.fr

Serial

1792644497

Refresh / retry

10800 s / 3600 s

Expire

604800 s

Negative TTL

3600 s

Serial per nameserver

Checks

• !

  Serials differ

  The nameservers serve different versions of the zone: 1792639143 on ns3.impreza.host (162.251.82.118); 1792644380 on ns2.impreza.host (162.251.82.249), ns2.impreza.host (162.251.82.121), ns2.impreza.host (162.251.82.248); 1792644496 on ns1.impreza.host (162.251.82.123), ns1.impreza.host (162.251.82.250), ns3.impreza.host (162.251.82.247), ns3.impreza.host (162.251.82.246), ns4.impreza.host (162.251.82.252), ns4.impreza.host (162.251.82.253), ns4.impreza.host (162.251.82.125); 1792644497 on ns1.impreza.host (162.251.82.251); 1792644535 on ns3.impreza.host (162.251.82.119); 1792644555 on ns4.impreza.host (162.251.82.124); 1792644819 on ns1.impreza.host (162.251.82.122), ns2.impreza.host (162.251.82.120). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

  #22
• ✓ Timers within recommendations #23

  SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
• i

  Hidden master (not resolvable)

  The primary nameserver 208.91.197.91 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 hostmaster@primebonus.fr #25

  The SOA RNAME hostmaster.primebonus.fr means hostmaster@primebonus.fr.
• ✓ Timestamp serial #26

  The serial 1792644497 is a Unix timestamp (2026-10-22 04:48 UTC).

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

2 records at the apex

Found

Read from

162.251.82.251:53

Checks

• !

  Very low TTLs

  These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.

  #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