lovelybooks.de

Checked 21 October 2026, 23:20 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 warnings 0 failed 7 info

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

ns01.paragon-systems.de, ns02.paragon-systems.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns01.paragon-systems.de, ns02.paragon-systems.de
NS in the zone
ns01.paragon-systems.de, ns02.paragon-systems.de
NameserverAddressesNetwork (AS)Glue
ns01.paragon-systems.de195.160.160.61AS12360 KTK - KEVAG Telekom GmbH, DE195.160.160.61
ns02.paragon-systems.de195.160.161.62AS12360 KTK - KEVAG Telekom GmbH, DE195.160.161.62

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.paragon-systems.de, ns02.paragon-systems.de.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS12360 (KTK - KEVAG Telekom GmbH, DE): 2 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 .de
    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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.paragon-systems.de 195.160.160.61NOERROR, 6 ms, authoritativenoyes / yesrefuseddisabled
ns02.paragon-systems.de 195.160.161.62NOERROR, 4 ms, authoritativenoyes / yesrefuseddisabled

Checks

  • ✓ All respond #14
    All 2 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns01.paragon-systems.de: "disabled"; ns02.paragon-systems.de: "disabled".
    #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.

SOA

pass

serial 2026051900 · primary ns01.paragon-systems.de

Found

Primary (MNAME)
ns01.paragon-systems.de
Contact (RNAME)
dns.paragon-systems.de
Serial
2026051900
Refresh / retry
21600 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns01.paragon-systems.de (195.160.160.61)2026051900
ns02.paragon-systems.de (195.160.161.62)2026051900

Checks

  • ✓ Serial 2026051900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.paragon-systems.de is one of the listed nameservers.
  • ✓ Contact dns@paragon-systems.de #25
    The SOA RNAME dns.paragon-systems.de means dns@paragon-systems.de.
  • ✓ Date-based serial #26
    The serial 2026051900 follows the YYYYMMDDnn convention (2026-05-19).

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

16 records at the apex

Found

Read from
195.160.160.61:53
TypeValueTTL
SOAns01.paragon-systems.de. dns.paragon-systems.de. 2026051900 21600 7200 604800 864003600
NSns01.paragon-systems.de.3600
NSns02.paragon-systems.de.3600
A195.160.160.893600
MX5 alt2.aspmx.l.google.com.3600
MX1 aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX10 alt4.aspmx.l.google.com.3600
MX10 alt3.aspmx.l.google.com.3600
TXT"google-site-verification=HyLyiZwEolER-mOlX_uaIQB2u6UTZ_mg1W1zGom7BlI"3600
TXT"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQClxeNKzad8qvVGv3v7Nb9JjQvs9HdVYvrtQq0bPiUGDScL5avuRtS4htGP5huAMf/EAezy6/qOVkga6ZulYBkmUI+belT7YOHbsNYkFBFg/vEQIMcDL25tOvTCNqZDc8RnzdkERQh05uIRoVFA2h/kpzDbU3qXlGY8TuBVvG116wIDAQAB;"3600
TXT"google-site-verification=fyRtK5sHmuK819MAcioGjIz8hdyzTvQnnibLUDhmAGk"3600
TXT"facebook-domain-verification=fwabb8jv5hh31wfejhtidb9oi06zqu"3600
TXT"google-site-verification=-BqUnkJpkScaY6CpgOTH4BIaJEyJF7TFW4Gp9IXnnEk"3600
TXT"google-site-verification=I1xvhQEojsjf62W4_n_r9HNWdQqA-NDYaaco4KFq7aI"3600
TXT"google-site-verification=uL3HrgbQQw6n6OChtzEzt7oJbdQ6Qji0Em6H-PFtr-0"3600

Checks

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