best-gpu.ruDomain 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.

From a full browser scan of the homepage on 23 Oct 2026, with no consent given. Results can differ by country and page.

• IPv6No IPv6 address
  No
• DNSSECDNS answers aren’t signed
  No
• CAA recordAny CA may issue certificates
  No
• HSTS preloadNot on the browsers’ preload list
  No

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

• Xxn--90adaua4aqvf.xn--p1aiReport → for xn--90adaua4aqvf.xn--p1ai
• Xxn-----8kcaharbbaeum7aghgsoeia7amkwkb.xn--p1aiReport → for xn-----8kcaharbbaeum7aghgsoeia7amkwkb.xn--p1ai
• Xxn------6cdcjs0ascbbdmpicfgcbdjs7avfnc1fxj.xn--p1aiReport → for xn------6cdcjs0ascbbdmpicfgcbdjs7avfnc1fxj.xn--p1ai
• Xxn----77-53dkc5detui6akk0k.xn--p1aiReport → for xn----77-53dkc5detui6akk0k.xn--p1ai
• Xxn----54-93dhghhu0c9ac.xn--p1aiReport → for xn----54-93dhghhu0c9ac.xn--p1ai
• Xxn----ctbe4awafew.xn--p1aiReport → for xn----ctbe4awafew.xn--p1ai
• Xxn-----8kcfl2aeohldcdc0b.xn--p1aiReport → for xn-----8kcfl2aeohldcdc0b.xn--p1ai
• Xxn--90abjbmanmfsww2lnb.xn--p1aiReport → for xn--90abjbmanmfsww2lnb.xn--p1ai
• Xxn----39-43dzgver5cqhcqg7mk.xn--p1aiReport → for xn----39-43dzgver5cqhcqg7mk.xn--p1ai
• Xxn--74-mlca2anhw.xn--p1aiReport → for xn--74-mlca2anhw.xn--p1ai

No reviews yet. Used best-gpu.ru? Be the first to say how it went.

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

We couldn't find an IP address for best-gpu.ru's web or mail servers to check.

No subdomains found in the certificate transparency logs.

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