8407.twDomain analysis & security report

• SPFMissing

  No SPF record: any server can send mail that claims to come from this domain.

  —
• DKIMNot found

  No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.

  —
• DMARCMissing

  No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.

  —
• MTA-STSMissing

  Forces encrypted delivery between mail servers.

  —
• BIMINot found

  Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.

  —

Read from the domain's public DNS records.

Running a full browser scan of the homepage… This takes about a minute.

From CubDomain's daily newly registered domains. Similar doesn't mean malicious.

• 0009387.vipReport → for 009387.vip
• 0038795.vipReport → for 038795.vip
• 0067248.vipReport → for 067248.vip
• 003016.twReport → for 03016.tw
• 0053547.vipReport → for 053547.vip
• 994308.myReport → for 94308.my
• 112682.ioReport → for 12682.io
• 0026454.vipReport → for 026454.vip
• 00325.bzReport → for 0325.bz
• 0023270.vipReport → for 023270.vip

No reviews yet. Used 8407.tw? Be the first to say how it went.

Reviews are from CubDomain users and are separate from the security verdicts above.

Searching the certificate transparency logs… This can take up to a minute.

No changes seen since we started recording on 13 Nov 2026.