Domain report: mailjet.de

Registration

info

.de country-code

Found

TLD: .de (country-code)
ICANN policies apply: no

Checks

i

.de 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

.de is delegated in the root zone and DNSSEC-signed.
i

Registration data not available

No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.

#3

Delegation

warn

ns0.mljt.tech, ns1.mljt.tech, ns2.mljt.tech

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: ns0.mljt.tech, ns1.mljt.tech, ns2.mljt.tech
NS in the zone: ns0.mljt.tech, ns1.mljt.tech, ns2.mljt.tech

Nameserver	Addresses	Network (AS)	Glue
ns0.mljt.tech	104.199.73.221	AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US	-
ns1.mljt.tech	35.238.164.182	AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US	-
ns2.mljt.tech	212.47.237.20	AS12876 AS12876 - Scaleway SAS, FR	-

Checks

✓ 3 nameservers #6

Delegated to ns0.mljt.tech, ns1.mljt.tech, ns2.mljt.tech.
✓ 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 0 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS12876 (AS12876 - Scaleway SAS, FR): 1 address; AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US): 2 addresses.
i

All nameserver names under .tech

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

3 of 3 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns0.mljt.tech 104.199.73.221	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns1.mljt.tech 35.238.164.182	NOERROR, 113 ms, authoritative	no	yes / yes	refused	-
ns2.mljt.tech 212.47.237.20	NOERROR, 15 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 3 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

warn

serial 2019122762 · primary ns0.mljt.tech

Found

Primary (MNAME): ns0.mljt.tech
Contact (RNAME): abuse.mailjet.com
Serial: 2019122762
Refresh / retry: 14400 s / 900 s
Expire: 604800 s
Negative TTL: 180 s

Serial per nameserver

Nameserver	Serial
ns0.mljt.tech (104.199.73.221)	2019122762
ns1.mljt.tech (35.238.164.182)	2019122762
ns2.mljt.tech (212.47.237.20)	2019122762

Checks

✓ Serial 2019122762 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 4h, retry 15m, expire 7d, negative TTL 3m.

#23
✓ Primary is a public nameserver #24

The primary nameserver ns0.mljt.tech is one of the listed nameservers.
✓ Contact abuse@mailjet.com #25

The SOA RNAME abuse.mailjet.com means abuse@mailjet.com.
✓ Date-based serial #26

The serial 2019122762 follows the YYYYMMDDnn convention (2019-12-27).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC
Signatures valid until: 2 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
24471	ECDSAP256SHA256 (13)	SHA256 EF1C72136A2344A5…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
54821	ZSK (256)	ECDSAP256SHA256 (13)
24471	KSK (257)	ECDSAP256SHA256 (13)

Checks

✓ Signed and validated #27

The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
✓ DS matches a key #28

The DS record at the parent matches a key in the zone: key tag 24471 (SHA256).
✓ Modern algorithms #29

Key algorithms: ECDSAP256SHA256 (13).
✓ Signatures valid until 2026-11-02 #30

The earliest DNSKEY/SOA signature expires at 2026-11-02 08:15 UTC.
i

NSEC

The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.

#31

Records

info

20 records at the apex

Found

Read from: 104.199.73.221:53

Type	Value	TTL
SOA	ns0.mljt.tech. abuse.mailjet.com. 2019122762 14400 900 604800 180	7200
NS	ns0.mljt.tech.	7200
NS	ns1.mljt.tech.	7200
NS	ns2.mljt.tech.	7200
A	141.193.213.10	600
A	141.193.213.11	600
MX	1 aspmx.l.google.com.	7200
MX	5 alt1.aspmx.l.google.com.	7200
MX	5 alt2.aspmx.l.google.com.	7200
MX	10 aspmx2.googlemail.com.	7200
MX	10 aspmx3.googlemail.com.	7200
MX	10 aspmx4.googlemail.com.	7200
MX	10 aspmx5.googlemail.com.	7200
TXT	"v=spf1 -all"	7200
TXT	"_jqpw21v55djrhxspful88ms6pmyitih"	7200
TXT	"_rxla9bon31ul7v3d7giuzcpk3m1vmjg"	7200
TXT	"vzzzkpg29mlsrs9q11txhxcfkdlsgvt0"	7200
TXT	"wsh389lr03ww9m7x45d534qzzp62m54d"	7200
TXT	"google-site-verification=E9JenAd7yrCkFL95sOz5hAWfNVp7u-TCuNw-t9g9loc"	7200
TXT	"google-site-verification=JlGHFbX-eKFKk5VB7gBCLZoCoGr-kamsfnBF7OuNOa8"	7200

Checks

✓ TTLs within range #32

TTLs: A 10m, MX 2h, NS 2h. The NS TTL at the parent is 1d and in the zone 2h; 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