SurfaceMap › a › allianz.de

allianz.de

Checked 2026-10-21 21:28 UTC · first added 2026-10-21
!Passed with warnings Score 79 of 100

Domain & DNS

warn

20 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers iSOA !DNSSEC !Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns4.allianz.de (glue 195.253.116.8, 2a01:5b0:34::8, zone 195.253.116.8, 184.26.160.66, 2.16.40.66, 2600:1480:f000::42, 2600:1403:a::42, 2a01:5b0:34::8). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2.allianz.com: "48878.26"; ns2.allianz.com: "41824.6"; ns2.allianz.com: "41824.8"; ns2.allianz.com: "48878.30"; ns4.allianz.de: "48878.26"; ns4.allianz.de: "48878.32"; ns4.allianz.de: "48878.29"; ns6.az-ip.net: "41824.7"; ns6.az-ip.net: "41824.5"; ns6.az-ip.net: "41824.4"; ns6.az-ip.net: "41824.6". Hide or replace the version string.
    #17
  • !
    Not signed
    DNSSEC · 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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 3h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for allianz.de ›

Mail

warn

29 passed 3 warn 0 failed

Areas

✓SPF ✓DMARC !DKIM !DNSSEC !MX iTLS ✓BIMI

Problems

  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.hc1435-93.eu.iphmx.com, mx2.hc1435-93.eu.iphmx.com
    #11

Recent checks

!

Full report

Mail report for allianz.de ›