mondediplo.com

Checked 22 October 2026, 09:52 UTC · via 8.8.8.8
!Passed with warnings
25 passed 1 warning 0 failed 5 info

Registration

info

.com generic · Gandi SAS · expires 2032-12-14

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Gandi SAS
Registered
14 December 2001
Last changed
10 July 2026
Expires
14 December 2032
Status
client transfer prohibited
Registry nameservers
ns-110-b.gandi.net, ns-113-c.gandi.net, ns-220-a.gandi.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2032-12-14 #3
    The registration is valid until 2032-12-14 (2245 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

ns-110-b.gandi.net, ns-113-c.gandi.net, ns-220-a.gandi.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns-110-b.gandi.net, ns-113-c.gandi.net, ns-220-a.gandi.net
NS in the zone
ns-110-b.gandi.net, ns-113-c.gandi.net, ns-220-a.gandi.net
NameserverAddressesNetwork (AS)Glue
ns-110-b.gandi.net213.167.230.111 2001:4b98:aaab::6fAS29169 GANDI-AS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-113-c.gandi.net217.70.187.114 2604:3400:aaac::72AS29169 GANDI-AS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-220-a.gandi.net173.246.100.221 2001:4b98:aaaa::ddAS29169 GANDI-AS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns-110-b.gandi.net, ns-113-c.gandi.net, ns-220-a.gandi.net.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS209453 (GANDI-LIVEDNS - GANDI SAS, FR): 3 addresses; AS29169 (GANDI-AS - GANDI SAS, FR): 3 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-110-b.gandi.net 213.167.230.111NOERROR, 6 ms, authoritativenoyes / yesrefused-
ns-110-b.gandi.net 2001:4b98:aaab::6fNOERROR, 5 ms, authoritativenoyes / yesrefused-
ns-113-c.gandi.net 217.70.187.114NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-113-c.gandi.net 2604:3400:aaac::72NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-220-a.gandi.net 173.246.100.221NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-220-a.gandi.net 2001:4b98:aaaa::ddNOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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 1792627200 · primary ns1.gandi.net

Found

Primary (MNAME)
ns1.gandi.net
Contact (RNAME)
hostmaster.gandi.net
Serial
1792627200
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns-110-b.gandi.net (213.167.230.111)1792627200
ns-110-b.gandi.net (2001:4b98:aaab::6f)1792627200
ns-113-c.gandi.net (217.70.187.114)1792627200
ns-113-c.gandi.net (2604:3400:aaac::72)1792627200
ns-220-a.gandi.net (173.246.100.221)1792627200
ns-220-a.gandi.net (2001:4b98:aaaa::dd)1792627200

Checks

  • ✓ Serial 1792627200 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • i
    Hidden master
    The primary nameserver ns1.gandi.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@gandi.net #25
    The SOA RNAME hostmaster.gandi.net means hostmaster@gandi.net.
  • ✓ Timestamp serial #26
    The serial 1792627200 is a Unix timestamp (2026-10-22 00:00 UTC).

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

14 records at the apex

Found

Read from
213.167.230.111:53
TypeValueTTL
SOAns1.gandi.net. hostmaster.gandi.net. 1792627200 10800 3600 604800 1080010800
NSns-113-c.gandi.net.10800
NSns-220-a.gandi.net.10800
NSns-110-b.gandi.net.10800
A185.34.35.63600
MX5 ALT2.ASPMX.L.GOOGLE.com.3600
MX10 ASPMX3.GOOGLEMAIL.com.3600
MX1 ASPMX.L.GOOGLE.com.3600
MX5 ALT1.ASPMX.L.GOOGLE.com.3600
MX10 ASPMX2.GOOGLEMAIL.com.3600
MX10 ASPMX4.GOOGLEMAIL.com.3600
MX10 ASPMX5.GOOGLEMAIL.com.3600
TXT"v=spf1 include:spf.mailjet.com a mx include:spf.octopuce.fr include:_spf.google.com -all"10800
TXT"google-site-verification=iWsa52NlO0v84O898ATw1zTQkKsMp9kyhsX12Tj-Qzw"10800

Checks

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