freelancermap.de

Checked 21 October 2026, 22:31 UTC · via 8.8.8.8
!Passed with warnings
19 passed 1 warning 0 failed 9 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

info

ns1.ns-serve.net, ns2.ns-serve.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ns-serve.net, ns2.ns-serve.net
NS in the zone
ns1.ns-serve.net, ns2.ns-serve.net
NameserverAddressesNetwork (AS)Glue
ns1.ns-serve.net195.191.92.140 2001:67c:2394:2::1001AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE-
ns2.ns-serve.net195.191.93.140 2001:67c:2394:4::1001AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ns-serve.net, ns2.ns-serve.net.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:67c:2394::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS25504 (CRONON-AS - Vautron Rechenzentrum AG, DE): 4 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 .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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ns-serve.net 195.191.92.140NOERROR, 13 ms, authoritativenoyes / yesrefusedVautron
ns1.ns-serve.net 2001:67c:2394:2::1001NOERROR, 13 ms, authoritativenoyes / yesrefusedVautron
ns2.ns-serve.net 195.191.93.140NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.ns-serve.net 2001:67c:2394:4::1001NOERROR, 13 ms, authoritativenoyes / yesrefusedVautron

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.ns-serve.net: "Vautron"; ns2.ns-serve.net: "Vautron".
    #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 1791811466 · primary ns1.ns-serve.net

Found

Primary (MNAME)
ns1.ns-serve.net
Contact (RNAME)
root.ns1.ns-serve.net
Serial
1791811466
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.ns-serve.net (195.191.92.140)1791811466
ns1.ns-serve.net (2001:67c:2394:2::1001)1791811466
ns2.ns-serve.net (195.191.93.140)1791811466
ns2.ns-serve.net (2001:67c:2394:4::1001)1791811466

Checks

  • ✓ Serial 1791811466 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ns-serve.net is one of the listed nameservers.
  • ✓ Contact root@ns1.ns-serve.net #25
    The SOA RNAME root.ns1.ns-serve.net means root@ns1.ns-serve.net.
  • ✓ Timestamp serial #26
    The serial 1791811466 is a Unix timestamp (2026-10-12 13:24 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

12 records at the apex

Found

Read from
195.191.92.140:53
TypeValueTTL
SOAns1.ns-serve.net. root.ns1.ns-serve.net. 1791811466 10800 3600 604800 360014400
NSns1.ns-serve.net.14400
NSns2.ns-serve.net.14400
A31.172.113.3314400
MX0 freelancermap-de.mail.protection.outlook.com.3600
TXT"langdock-verify=idJsz_bvEwnzCp_ejxAc9vb8vN48mQ-Gd65Fs0G5cTU"86400
TXT"openai-domain-verification=dv-t8Ph0yNNV3sLG9RHAB7YeKh8"86400
TXT"v=spf1 a mx include:customeriomail.com include:_spf.xchangecloud.eu include:spf.protection.outlook.com include:eu.zcsend.net include:spf.zoho.eu include:eu.transmail.net ~all"3600
TXT"anthropic-domain-verification-a23tbs=CKktiywcFjpzkJUyiNd3Km4Ih"86400
TXT"MS=D6FB08C3EB3059EB87E36A03E231A456FC2A1B3A"14400
TXT"zoho-verification=zb56266141.zmverify.zoho.eu"86400
TXT"wv-confirmation:6cjn9rtatqosokww4w4ko40kko880ooco4kgwkosgk8kg080o4"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 4h, MX 1h, 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.
  • 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