SurfaceMap › r › renren.com

renren.com

Checked 2026-10-22 10:30 UTC · first added 2026-10-21
✗Problems found Score 59 of 100

Domain & DNS

fail

21 passed 3 warn 1 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC ✗Records

Problems

  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to renren.com.eo.dnse0.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: kama.dnspod.net: "DNSPod AUTHORITY DNS 7.3.2512.01"; lake.dnspod.net: "DNSPod AUTHORITY DNS 7.3.2512.01". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #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 renren.com ›

Mail

fail

8 passed 4 warn 1 failed

Areas

✗SPF !DMARC !DKIM !DNSSEC !MX iBIMI

Problems

  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23

Recent checks

✗

Full report

Mail report for renren.com ›