SurfaceMap › i › instagram.de

instagram.de

Checked 2026-10-21 23:00 UTC · first added 2026-10-21
✗Problems found Score 75 of 100

Domain & DNS

warn

22 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    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), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for instagram.de ›

Mail

fail

15 passed 3 warn 1 failed

Areas

✓SPF !DMARC ✗DKIM !DNSSEC !MX iBIMI

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.instagram.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:a@dmarcreports.facebook.com (needs instagram.de._report._dmarc.dmarcreports.facebook.com). Ask the report provider to publish the record, or check the address.
    #29

Recent checks

✗

Full report

Mail report for instagram.de ›