lafa.ooo was registered with Name.com, Inc. on 29 Oct 2026 and is hosted on AS16509 in United States. Its SSL certificate from Let's Encrypt is valid until 27 Jan 2027, and the site does not support HTTP/3.
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
0 of 5 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.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
4 of 6 recommended headers
Forces HTTPS on future visits.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows, and whether it publishes an llms.txt.
From robots.txt. “Partly blocked”: kept out of some pages, not the homepage. Not every crawler follows it. llms.txt is an optional guide some sites publish for AI assistants — it is not a ranking factor.
Pages and files that show who runs the site and how it handles data.
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.
370 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| iafa.ru | Look-alike characters | 25 Sept 2026 | Checking… | Report → |
| iafa.cn | Look-alike characters | 19 Sept 2026 | Checking… | Report → |
| lafa.name | Other extension | 4 Nov 2026 | Parked | Report → |
| alfa.pics | Typo | 3 Nov 2026 | No website | Report → |
| alfa.best | Typo | 30 Oct 2026 | No website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is lafa.ooo’s name taken on other extensions?
Every IP address lafa.ooo resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| lafa.ooo | 216.150.1.1 | 300 |
| Host | Name server | TTL |
|---|---|---|
| lafa.ooo | ns1lmy.name.com | 300 |
| lafa.ooo | ns2bkr.name.com | 300 |
| lafa.ooo | ns3ckl.name.com | 300 |
| lafa.ooo | ns4lny.name.com | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| lafa.ooo | ns1.name.com hostmaster.nsone.net 1793235197 43200 7200 1209600 3600 | 3600 |
Other domains served from 216.150.1.1. Normal for shared hosting and CDNs.
No reviews yet. Used lafa.ooo? 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.
lafa.ooo has no community safety rating yet. Its SSL certificate is valid until 27 Jan 2027. See Security →
lafa.ooo is registered through Name.com, Inc. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expires on 29 Oct 2027 — in 11 months. See Overview →
lafa.ooo was registered on 29 Oct 2026, making it 10 days old. See Overview →
lafa.ooo is served from 1 IP address, mainly on AS16509 in United States. See Hosting →
Raw registry data for lafa.ooo. May be redacted by privacy services.
Domain Name: LAFA.OOO Registry Domain ID: D662925654-CNIC Registrar WHOIS Server: whois.name.com Registrar URL: http://www.name.com Updated Date: 2026-10-29T00:53:20Z Creation Date: 2026-10-29T00:53:15Z Registrar Registration Expiration Date: 2027-10-29T23:59:59Z Registrar: Name.com, Inc. Registrar IANA ID: 625 Reseller: Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited Domain Status: serverTransferProhibited https://www.icann.org/epp#serverTransferProhibited Registry Registrant ID: Not Available From Registry Registrant Name: Redacted For Privacy Registrant Organization: Domain Protection Services, Inc. Registrant Street: PO Box 1769 Registrant City: Denver Registrant State/Province: CO Registrant Postal Code: 80201 Registrant Country: US Registrant Phone: +1.7208009072 Registrant Fax: +1.7209758725 Registrant Email: https://www.name.com/contact-domain-whois/lafa.ooo Registry Admin ID: Not Available From Registry Admin Name: Redacted For Privacy Admin Organization: Domain Protection Services, Inc. Admin Street: PO Box 1769 Admin City: Denver Admin State/Province: CO Admin Postal Code: 80201 Admin Country: US Admin Phone: +1.7208009072 Admin Fax: +1.7209758725 Admin Email: https://www.name.com/contact-domain-whois/lafa.ooo Registry Tech ID: Not Available From Registry Tech Name: Redacted For Privacy Tech Organization: Domain Protection Services, Inc. Tech Street: PO Box 1769 Tech City: Denver Tech State/Province: CO Tech Postal Code: 80201 Tech Country: US Tech Phone: +1.7208009072 Tech Fax: +1.7209758725 Tech Email: https://www.name.com/contact-domain-whois/lafa.ooo Name Server: ns1lmy.name.com Name Server: ns2bkr.name.com Name Server: ns3ckl.name.com Name Server: ns4lny.name.com DNSSEC: unSigned Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.7203101849 URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-11-07T22:00:23Z <<< For more information on Whois status codes, please visit https://icann.org/epp The data in the Name.com, Inc. WHOIS database is provided by Name.com, Inc. for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Name.com, Inc. does not guarantee its accuracy. Users accessing the Name.com, Inc. WHOIS service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Name.com, Inc., except as reasonably necessary to register domain names or modify existing registrations. When using the Name.com, Inc. WHOIS service, please consider the following: the WHOIS service is not a replacement for standard EPP commands to the SRS service. WHOIS is not considered authoritative for registered domain objects. The WHOIS service may be scheduled for downtime during production or OT&E maintenance periods. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis, for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://www.name.com/layered-access-request . Name.com, Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
The first response from http://www.lafa.ooo, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with lafa.ooo. Data is collected independently from public sources and some figures are estimates, provided for information only.
Shares more of the URL with other sites than it needs to.
Restricts camera, microphone and other browser features.
From the homepage's response, https://vercel.com/login?next=%2Fsso-api%3Furl%3Dhttps%253A%252F%252Flafa.ooo%252F%26nonce%3D1dd1c38f6ab40883ab00a75029014f4953f48a5786e650a4905e509e0b991467
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 7 Nov 2026.