SurfaceMap › t › twitter.com

twitter.com

Checked 2026-10-22 11:14 UTC · first added 2026-10-21
!Passed with warnings Score 82 of 100

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2024011501 on a.r06.twtrdns.net (205.251.192.179), b.r06.twtrdns.net (205.251.196.198), b.u06.twtrdns.net (205.251.196.198), c.r06.twtrdns.net (205.251.194.151), c.u06.twtrdns.net (205.251.194.151), d.r06.twtrdns.net (205.251.199.195), d.u06.twtrdns.net (205.251.199.195); 2024169648 on a.u06.twtrdns.net (204.74.111.101). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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

Recent checks

!

Full report

Domain & DNS report for twitter.com ›

Mail

warn

26 passed 3 warn 0 failed

Areas

✓SPF ✓DMARC !DKIM !DNSSEC ✓MX !TLS iBIMI

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits), google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for twitter.com ›