Domain report: foren-city.de

Registration

info

.de country-code

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

warn

ns1.sedoparking.com, ns2.sedoparking.com

Nameserver	Addresses	Network (AS)	Glue
ns1.sedoparking.com	91.195.241.8 3.130.216.63	AS47846 SEDO-AS - SEDO GmbH, DE AS16509 AMAZON-02 - Amazon.com, Inc., US	-
ns2.sedoparking.com	91.195.240.8 34.211.188.210	AS47846 SEDO-AS - SEDO GmbH, DE AS16509 AMAZON-02 - Amazon.com, Inc., US	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.sedoparking.com, ns2.sedoparking.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 4 IPv4 /24s and 0 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses; AS47846 (SEDO-AS - SEDO GmbH, DE): 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
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

fail

4 of 4 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.sedoparking.com 91.195.241.8	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-
ns1.sedoparking.com 3.130.216.63	NOERROR, 110 ms, authoritative	no	yes / yes	refused	-
ns2.sedoparking.com 91.195.240.8	NOERROR, 11 ms, authoritative	OPEN	yes / yes	refused	-
ns2.sedoparking.com 34.211.188.210	NOERROR, 174 ms, authoritative	no	yes / yes	refused	-

✓ All respond #14

All 4 nameserver addresses answered.
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✗

Open recursion

These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: ns2.sedoparking.com (91.195.240.8). Disable recursion on authoritative servers.

#16
✓ 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.

pass

serial 2018051601 · primary ns1.sedoparking.com

✓ Serial 2018051601 everywhere #22

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

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

The primary nameserver ns1.sedoparking.com is one of the listed nameservers.
✓ Contact hostmaster@sedo.de #25

The SOA RNAME hostmaster.sedo.de means hostmaster@sedo.de.
✓ Date-based serial #26

The serial 2018051601 follows the YYYYMMDDnn convention (2018-05-16).

warn

Not signed

info

6 records at the apex

Type	Value	TTL
SOA	ns1.sedoparking.com. hostmaster.sedo.de. 2018051601 86400 10800 604800 86400	86400
NS	ns2.sedoparking.com.	86400
NS	ns1.sedoparking.com.	86400
A	64.190.63.222	14399
MX	0 localhost.	3600
TXT	"v=spf1 -all"	3600