Domain report: volkon.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

info

ns01.one.com, ns02.one.com

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: ns01.one.com, ns02.one.com
NS in the zone: ns01.one.com, ns02.one.com

Nameserver	Addresses	Network (AS)	Glue
ns01.one.com	195.206.121.10 2001:67c:28cc::10	AS197495 ONECOM-INFRA - One.com A/S, DK AS197495 ONECOM-INFRA - One.com A/S, DK	-
ns02.one.com	185.10.11.10 2001:67c:3c0::10	AS51468 ONECOM - One.com A/S, DK AS51468 ONECOM - One.com A/S, DK	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.one.com, ns02.one.com.

#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 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS197495 (ONECOM-INFRA - One.com A/S, DK): 2 addresses; AS51468 (ONECOM - One.com A/S, DK): 2 addresses.
i

All nameserver names under .com

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

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns01.one.com 195.206.121.10	NOERROR, 22 ms, authoritative	no	yes / yes	refused	-
ns01.one.com 2001:67c:28cc::10	NOERROR, 21 ms, authoritative	no	yes / yes	refused	-
ns02.one.com 185.10.11.10	NOERROR, 21 ms, authoritative	no	yes / yes	refused	-
ns02.one.com 2001:67c:3c0::10	NOERROR, 21 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

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

pass

serial 2026101804 · primary ns01.one.com

Found

Primary (MNAME): ns01.one.com
Contact (RNAME): hostmaster.one.com
Serial: 2026101804
Refresh / retry: 14400 s / 3600 s
Expire: 1209600 s
Negative TTL: 600 s

Serial per nameserver

Nameserver	Serial
ns01.one.com (195.206.121.10)	2026101804
ns01.one.com (2001:67c:28cc::10)	2026101804
ns02.one.com (185.10.11.10)	2026101804
ns02.one.com (2001:67c:3c0::10)	2026101804

Checks

✓ Serial 2026101804 everywhere #22

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

SOA refresh 4h, retry 1h, expire 14d, negative TTL 10m.
✓ Primary is a public nameserver #24

The primary nameserver ns01.one.com is one of the listed nameservers.
✓ Contact hostmaster@one.com #25

The SOA RNAME hostmaster.one.com means hostmaster@one.com.
✓ Date-based serial #26

The serial 2026101804 follows the YYYYMMDDnn convention (2026-10-18).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 0 iterations, 0-byte salt
Signatures valid until: 5 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
64534	ECDSAP256SHA256 (13)	SHA256 A5AC7E8C5777D733…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
53587	ZSK (256)	ECDSAP256SHA256 (13)
64534	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 64534 (SHA256).
✓ Modern algorithms #29

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

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

9 records at the apex

Found

Read from: 195.206.121.10:53

Type	Value	TTL
SOA	ns01.one.com. hostmaster.one.com. 2026101804 14400 3600 1209600 600	14400
NS	ns01.one.com.	14400
NS	ns02.one.com.	14400
A	46.30.213.146	3600
AAAA	2a02:2350:5:10c:94:3b83:cf92:8aaf	3600
MX	10 mx2.mailpod15-cph3.g1i.one.com.	10800
MX	10 mx4.mailpod15-cph3.g1i.one.com.	10800
MX	10 mx1.mailpod15-cph3.g1i.one.com.	10800
MX	10 mx3.mailpod15-cph3.g1i.one.com.	10800

Checks

✓ TTLs within range #32

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