ak-berlin.de

Checked 21 October 2026, 21:28 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 4 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

fm-unix.f-m-computer.de, ns2.fmc.berlin

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
fm-unix.f-m-computer.de, ns2.fmc.berlin
NS in the zone
fm-unix.f-m-computer.de, ns2.fmc.berlin
NameserverAddressesNetwork (AS)Glue
fm-unix.f-m-computer.de212.91.246.11AS15366 DNSNET - DNS:NET Internet Service GmbH, DE212.91.246.11
ns2.fmc.berlin104.40.159.233AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: fm-unix.f-m-computer.de, ns2.fmc.berlin.
    #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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15366 (DNSNET - DNS:NET Internet Service GmbH, DE): 1 address; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .berlin, .de.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
fm-unix.f-m-computer.de 212.91.246.11NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns2.fmc.berlin 104.40.159.233NOERROR, 12 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 99 · primary fm-unix.f-m-computer.de

Found

Primary (MNAME)
fm-unix.f-m-computer.de
Contact (RNAME)
hostmaster.f-m-computer.de
Serial
99
Refresh / retry
900 s / 600 s
Expire
86400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
fm-unix.f-m-computer.de (212.91.246.11)99
ns2.fmc.berlin (104.40.159.233)99

Checks

  • ✓ Serial 99 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 15m, retry 10m, expire 1d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver fm-unix.f-m-computer.de is one of the listed nameservers.
  • ✓ Contact hostmaster@f-m-computer.de #25
    The SOA RNAME hostmaster.f-m-computer.de means hostmaster@f-m-computer.de.
  • ✓ Counter serial #26
    The serial 99 is a plain counter.

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

9 records at the apex

Found

Read from
212.91.246.11:53
TypeValueTTL
SOAfm-unix.f-m-computer.de. hostmaster.f-m-computer.de. 99 900 600 86400 36003600
NSns2.fmc.berlin.3600
NSfm-unix.f-m-computer.de.3600
A78.47.83.1943600
MX0 akberlin-de0e.mail.protection.outlook.com.3600
TXT"MS=ms95255038"3600
TXT"v=spf1 a a:mxlbpu.ispgateway.de ip4:62.141.58.219 include:spf.crsend.com include:_spf.fmc.berlin include:_spf_eucentral1.prod.hydra.sophos.com include:spf.protection.outlook.com -all"3600
TXT"apple-domain-verification=IWuaQrIUBeVxcM32"3600
TXT"sophos-domain-verification=1c5823a3c7484c8556156341fab985c389555037"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