beet.ir is registered with whois.nic.ir and is hosted on AS43754 in Iran. Its SSL certificate doesn't cover this domain name, so browsers warn visitors.
What security vendors and the WOT community say about this domain.
1 of 5 protections set up
Lists the servers allowed to send email for this domain.
v=spf1 ip4:91.207.205.36 ip4:78.46.198.83 ip4:94.130.32.126 ip4:94.130.210.77 ip4:10.1.21.2 ip4:185.55.225.11 +a +mx ~allNo key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
527 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 6eet.com | Look-alike characters | 15 Sept 2026 | Active website | Report → |
| 6eet.top | Look-alike characters | 4 Sept 2026 | No website | Report → |
| ebet.mom | Typo | 27 Oct 2026 | Active website | Report → |
| beet.tattoo | Other extension | 15 Oct 2026 | Active website | Report → |
| bete.com.br | Typo | 8 Oct 2026 | No website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is beet.ir’s name taken on other extensions?
2 technologies detected across 2 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address beet.ir resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| beet.ir | 91.207.205.36 | 14400 |
| Host | Mail server | TTL |
|---|---|---|
| beet.ir | 0 beet.ir | 14400 |
| Host | Name server | TTL |
|---|---|---|
| beet.ir | ns97.accessdeny.net | 86400 |
| beet.ir | ns98.accessdeny.net | 86400 |
| Host | Text | TTL |
|---|---|---|
| beet.ir | "v=spf1 ip4:91.207.205.36 ip4:78.46.198.83 ip4:94.130.32.126 ip4:94.130.210.77 ip4:10.1.21.2 ip4:185.55.225.11 +a +mx ~all" | 14400 |
| Host | Start of authority | TTL |
|---|---|---|
| beet.ir | ns97.accessdeny.net cp-w-ir.talahost.net 2026052601 3600 1800 1209600 86400 | 86400 |
Other domains served from 91.207.205.36. Normal for shared hosting and CDNs.
No reviews yet. Used beet.ir? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
beet.ir has no community safety rating yet. Its SSL certificate doesn't cover this domain name, so browsers warn visitors. See Security →
beet.ir is registered through whois.nic.ir. See WHOIS →
beet.ir is served from 1 IP address, mainly on AS43754 in Iran. See Hosting →
We detected 2 technologies, including WordPress and jQuery. See Built with →
Raw registry data for beet.ir. May be redacted by privacy services.
% This is the IRNIC Whois server v2.0.0. % Available on web at http://whois.nic.ir/ % Find the terms and conditions of use on http://www.nic.ir/ % % This server uses UTF-8 as the encoding for requests and responses. % NOTE: This output has been filtered. % Information related to 'beet.ir' domain: beet.ir ascii: beet.ir remarks: The information about this domain is hidden by the domain holder nserver: ns2.domaincity.ir nserver: ns1.domaincity.ir source: IRNIC
The first response from http://www.beet.ir, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with beet.ir. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 30 Oct 2026.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.