300.pe is registered with kero.yachay.pe. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
0 of 4 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No 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.
—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.
We couldn't read an SSL certificate on port 443 when we last analysed 300.pe. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
589 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 3oo.rest | Look-alike characters | 14 Nov 2026 | Checking… | Report → |
| 3o0.net | Look-alike characters | 28 Oct 2026 | Active website | Report → |
| 30o.com.br | Look-alike characters | 15 Sept 2026 | Checking… | Report → |
| 3o0.buzz | Look-alike characters | 4 Sept 2026 | No website | Report → |
| 3oo.app | Look-alike characters | 31 Aug 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is 300.pe’s name taken on other extensions?
| Host | Name server | TTL |
|---|---|---|
| 300.pe | freedns1.registrar-servers.com | 1800 |
| 300.pe | freedns2.registrar-servers.com | 1800 |
| 300.pe | freedns3.registrar-servers.com | 1800 |
| 300.pe | freedns4.registrar-servers.com | 1800 |
| 300.pe | freedns5.registrar-servers.com | 1800 |
| Host | Start of authority | TTL |
|---|---|---|
| 300.pe | freedns1.registrar-servers.com hostmaster.registrar-servers.com 1751833869 43200 3600 604800 3601 | 3601 |
No reviews yet. Used 300.pe? 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.
300.pe has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
300.pe is registered through kero.yachay.pe. The public WHOIS record shows the registrant’s details. See WHOIS →
Raw registry data for 300.pe. May be redacted by privacy services.
Domain Name: 300.pe Sponsoring Registrar: NIC.PE Domain Status: ok Registrant Name: Land Resolution & Planetary Peace Union - 300.UNION Admin Name: Land Resolution & Planetary Peace Union - 300.UNION Admin Email: pro1ice@yahoo.com Name Server: freedns1.registrar-servers.com Name Server: freedns2.registrar-servers.com Name Server: dell.ns.cloudflare.com Name Server: lennon.ns.cloudflare.com >>> Last update of WHOIS database: 2026-11-20T05:25:58.574Z <<< La informacion de esta pagina se provee exclusivamente para fines relacionados con la delegacion de nombres de dominios, su publicidad y la operacion del DNS administrado por el NIC .Pe. Queda absolutamente prohibido el uso de los datos proporcionados para cualquier otra finalidad distinta a la indicada, incluyendo el envio de correo electronico comercial no solicitado, de acuerdo a lo dispuesto en la Ley N 28493 - Ley Peruana Antispam. La base de datos generada a partir del sistema de delegacion de nombres de dominio peruanos esta protegida por las leyes nacionales de Propiedad Intelectual y los tratados internacionales que sobre la materia ha suscrito el Peru. En ese sentido, su autorizacion es exclusivamente para visualizar y conocer el contenido de la misma, por lo que queda expresamente prohibida su reproduccion, comunicacion, distribucion, transformacion y cualquier otro uso distinto al autorizado.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with 300.pe. 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 20 Nov 2026.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.