SurfaceMap › t › tweetdeck.com

tweetdeck.com

Checked 2026-10-22 11:13 UTC · first added 2026-10-21
✗Problems found Score 46 of 100

Domain & DNS

fail

21 passed 5 warn 1 failed

Areas

iRegistration !Delegation iNameservers ✗SOA !DNSSEC iRecords

Problems

  • ✗
    Invalid contact address
    SOA · The SOA RNAME "noc\\@twitter.com" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: a.r08.twtrdns.net, b.r08.twtrdns.net, c.r08.twtrdns.net, d.r08.twtrdns.net. a.r08.twtrdns.net, a.u08.twtrdns.net, b.r08.twtrdns.net, b.u08.twtrdns.net, c.r08.twtrdns.net, c.u08.twtrdns.net, d.r08.twtrdns.net, d.u08.twtrdns.net report NS a.r08.twtrdns.net a.u08.twtrdns.net b.r08.twtrdns.net b.u08.twtrdns.net c.r08.twtrdns.net c.u08.twtrdns.net d.r08.twtrdns.net d.u08.twtrdns.net.
    #7
  • !
    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: 2023030801 on a.r08.twtrdns.net (205.251.196.52), b.r08.twtrdns.net (205.251.192.103), c.r08.twtrdns.net (205.251.195.152), d.r08.twtrdns.net (205.251.199.230); 2023188866 on a.u08.twtrdns.net (204.74.66.101), b.u08.twtrdns.net (204.74.67.101), c.u08.twtrdns.net (204.74.110.101), d.u08.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
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 10m, expire 7d, negative TTL 1m.
    #23
  • !
    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 tweetdeck.com ›

Mail

fail

16 passed 3 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.tweetdeck.com 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
  • !
    More than 5 MX records
    MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    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 tweetdeck.com ›