SurfaceMap › l › lofter.com

lofter.com

Checked 2026-10-22 09:40 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

23 passed 4 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: lofterns4.netease.com (glue 18.179.234.142, zone 18.179.234.142, 3.222.70.58). Update the glue at your registrar.
    #8
  • !
    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: 20130922 on lofterns3.netease.com (42.186.102.140); 20130923 on lofterns1.netease.com (112.126.80.178), lofterns1.netease.com (1.95.235.8), lofterns3.netease.com (42.186.146.27), lofterns4.netease.com (18.179.234.142), lofterns4.netease.com (3.222.70.58). 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 lofter.com ›

Mail

fail

16 passed 4 warn 1 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 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: mx.qiye.163.com, mx2.qiye.163.com
    #11
  • !
    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 lofter.com ›