lofi.co

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 71 days left7 years old

One re-check per domain each UTC day.

70

lofi.co was registered on 4 Jun 2019 via CSC Corporate Domains, Inc. and the registry expiry is 4 Jun 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/lofi.co.

lofi.co publishes 2 nameservers. DNSSEC is not signed.

lofi.co has 1 IPv4 address (199.36.158.100) and 1 IPv6 address (2620:0:890::100). The geolocation database places 199.36.158.100 in Mountain View, United States.

The TLS certificate from WR3 is valid and has 71 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Firebase, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for lofi.co in the checks that ran.

Domain · RDAP/WHOIS

lofi.co was registered on 4 Jun 2019 via CSC Corporate Domains, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.registry.co/co/domain/lofi.co.

Registeredsince 4 Jun 2019
Created4 June 2019
Updated31 May 2026
Expires4 June 2027
RegistrarCSC Corporate Domains, Inc.
Statusclient transfer prohibited
Nameserversjune.ns.cloudflare.com, amir.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.registry.co/co/domain/lofi.co

lofi.co carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

Nameserver june.ns.cloudflare.com is published for lofi.co in the registration record from https://rdap.registry.co/co/domain/lofi.co.

Nameserver amir.ns.cloudflare.com is published for lofi.co in the registration record from https://rdap.registry.co/co/domain/lofi.co.

DNS

lofi.co has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A199.36.158.100
AAAA2620:0:890::100
NSamir.ns.cloudflare.com, june.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 199.36.158.100 answers for lofi.co at resolver 1.1.1.1:53.

IPv6 address 2620:0:890::100 answers for lofi.co at resolver 1.1.1.1:53.

Hosting and geo

lofi.co is placed in Mountain View, United States by the local geolocation database (db-ip).

Address199.36.158.100
CountryUnited States
CityMountain View
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for lofi.co is valid, with 71 days left and 2 subject alternative names. Source: tls:443.

IssuerWR3
Subjectlofi.co
Valid from13 October 2026
Valid until11 January 2027
Days left71
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: app.lofi.co, lofi.co.

Tech stack

Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.

  • Firebase · Databases, Development
  • HSTS · Security
  • HTTP/3 · Miscellaneous

Firebase is filed under Databases, Development.

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

On-page checks

The homepage returned HTTP 200 in 6 ms. The target title is 4 characters and the page has 0 H1 headings.

Status200
TTFB6 ms
Title length4 yes
Quoted title"Lofi"
Meta descriptionnone no
H1 count0
HSTSyes yes
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links1
Images3
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for lofi.co is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
CSPno

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 5 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: rdap created changed from empty to 2019-06-04T17:00:10.0Z.
  • October 2026: rdap dnssec changed from unknown to no.
  • October 2026: rdap expires changed from empty to 2027-06-04T23:59:59.0Z.
  • October 2026: rdap nameservers changed from empty to amir.ns.cloudflare.com,june.ns.cloudflare.com.
  • October 2026: rdap registered changed from unknown to yes.
  • October 2026: rdap registrar changed from empty to CSC Corporate Domains, Inc..
  • October 2026: rdap statuses changed from empty to client transfer prohibited.
  • October 2026: rdap updated changed from empty to 2026-05-31T05:02:02.0Z.
  • October 2026: geo city changed from empty to Mountain View.
  • October 2026: geo country changed from empty to United States.

Questions

Is lofi.co safe?

The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.

Who hosts lofi.co?

lofi.co is placed in Mountain View, United States.

When does lofi.co expire?

lofi.co expires on 4 June 2027 according to https://rdap.registry.co/co/domain/lofi.co.

Who owns lofi.co?

The registry did not return a person or a company for lofi.co. RDAP often redacts the registrant. The registrar on file is CSC Corporate Domains, Inc..

Sources

  • RDAP source https://rdap.registry.co/co/domain/lofi.co at 2026-10-30T13:39:06Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:39:06Z
  • TLS source tls:443 at 2026-10-30T13:39:06Z
  • HTTP source https://lofi.co/ at 2026-10-30T13:39:06Z
  • Tech source wappalyzergo at 2026-10-30T13:39:06Z
  • Geo source db-ip at 2026-10-30T13:39:06Z
  • Safety source family DNS and local lists at 2026-10-30T13:39:06Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.co CSC Corporate Domains, Inc.

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.