123proxy.app
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 83 days left5 years old
45
123proxy.app was registered on 5 Feb 2021 via Namecheap Inc. and the registry expiry is 5 Feb 2027. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/123proxy.app.
123proxy.app publishes 2 nameservers. DNSSEC is not signed.
123proxy.app has 2 IPv4 addresses (104.21.22.244, 172.67.207.223) and 2 IPv6 addresses (2606:4700:3032::6815:16f4, 2606:4700:3037::ac43:cfdf). The geolocation database places 104.21.22.244 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 83 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
123proxy.app was registered on 5 Feb 2021 via Namecheap Inc.. The registry returned 1 status value and 2 nameservers from https://pubapi.registry.google/rdap/domain/123proxy.app.
| Registered | since 5 Feb 2021 |
|---|---|
| Created | 5 February 2021 |
| Updated | 7 February 2026 |
| Expires | 5 February 2027 |
| Registrar | Namecheap Inc. |
| Status | client transfer prohibited |
| Nameservers | art.ns.cloudflare.com, haley.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/123proxy.app |
123proxy.app 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 art.ns.cloudflare.com is published for 123proxy.app in the registration record from https://pubapi.registry.google/rdap/domain/123proxy.app.
Nameserver haley.ns.cloudflare.com is published for 123proxy.app in the registration record from https://pubapi.registry.google/rdap/domain/123proxy.app.
DNS
123proxy.app has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.22.244, 172.67.207.223 |
|---|---|
| AAAA | 2606:4700:3032::6815:16f4, 2606:4700:3037::ac43:cfdf |
| NS | art.ns.cloudflare.com, haley.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.22.244 answers for 123proxy.app at resolver 1.1.1.1:53.
IPv4 address 172.67.207.223 answers for 123proxy.app at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::6815:16f4 answers for 123proxy.app at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:cfdf answers for 123proxy.app at resolver 1.1.1.1:53.
Hosting and geo
123proxy.app is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.22.244 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for 123proxy.app is valid, with 83 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | 123proxy.app |
| Valid from | 24 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 83 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.123proxy.app, 123proxy.app.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 30 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 30 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 123proxy.app is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | yes |
Cloudflare family DNS returned a block for 123proxy.app. That resolver covers adult and malware names.
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 10 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 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 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
First checked on 30 October 2026; changes will appear here.
Questions
Is 123proxy.app safe?
Cloudflare family DNS returned a block for 123proxy.app. That resolver covers adult and malware names.
Who hosts 123proxy.app?
123proxy.app is placed in Toronto, Canada.
When does 123proxy.app expire?
123proxy.app expires on 5 February 2027 according to https://pubapi.registry.google/rdap/domain/123proxy.app.
Who owns 123proxy.app?
The registry did not return a person or a company for 123proxy.app. RDAP often redacts the registrant. The registrar on file is Namecheap Inc..
Sources
- RDAP source https://pubapi.registry.google/rdap/domain/123proxy.app at 2026-10-30T13:31:18Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:31:18Z
- TLS source tls:443 at 2026-10-30T13:31:18Z
- HTTP source https://123proxy.app/ at 2026-10-30T13:31:18Z
- Tech source wappalyzergo at 2026-10-30T13:31:18Z
- Geo source db-ip at 2026-10-30T13:31:18Z
- Safety source family DNS and local lists at 2026-10-30T13:31:18Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.
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.