phimbl.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 70 days left10 years old
40
phimbl.net was registered on 30 Jun 2016 via GoDaddy.com, LLC and the registry expiry is 30 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/phimbl.net.
phimbl.net publishes 2 nameservers. DNSSEC is not signed.
phimbl.net has 1 IPv4 address (162.4.84.215). The geolocation database places 162.4.84.215 in Los Angeles, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
No safety warning was recorded for phimbl.net in the checks that ran.
Domain · RDAP/WHOIS
phimbl.net was registered on 30 Jun 2016 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/phimbl.net.
| Registered | since 30 Jun 2016 |
|---|---|
| Created | 30 June 2016 |
| Updated | 1 July 2026 |
| Expires | 30 June 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns1.parklogic.com, ns2.parklogic.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/phimbl.net |
phimbl.net carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
phimbl.net carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
phimbl.net 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.
phimbl.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns1.parklogic.com is published for phimbl.net in the registration record from https://rdap.verisign.com/net/v1/domain/phimbl.net.
Nameserver ns2.parklogic.com is published for phimbl.net in the registration record from https://rdap.verisign.com/net/v1/domain/phimbl.net.
DNS
phimbl.net has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.215 |
|---|---|
| AAAA | — |
| NS | ns1.parklogic.com, ns2.parklogic.com |
| MX | mx156.hostedmxserver.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at phimbl.net is "v=spf1 -all".
IPv4 address 162.4.84.215 answers for phimbl.net at resolver 1.1.1.1:53.
Mail exchanger mx156.hostedmxserver.com has preference 10.
A random label under phimbl.net also resolved, which means wildcard DNS is on.
A nameserver belongs to a parking host.
Hosting and geo
phimbl.net is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.215 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for phimbl.net is not valid, with 70 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | phimbl.net |
| Valid from | 12 October 2026 |
| Valid until | 10 January 2027 |
| Days left | 70 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: phimbl.net.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://phimbl.net/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for phimbl.net is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
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 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 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: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is phimbl.net 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 phimbl.net?
phimbl.net is placed in Los Angeles, United States.
When does phimbl.net expire?
phimbl.net expires on 30 June 2027 according to https://rdap.verisign.com/net/v1/domain/phimbl.net.
Who owns phimbl.net?
The registry did not return a person or a company for phimbl.net. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/phimbl.net at 2026-10-30T14:54:48Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:54:48Z
- TLS source tls:443 at 2026-10-30T14:54:48Z
- HTTP source https://phimbl.net/ at 2026-10-30T14:54:48Z
- Tech source not available at 2026-10-30T14:54:48Z
- Geo source db-ip at 2026-10-30T14:54:48Z
- Safety source family DNS and local lists at 2026-10-30T14:54:48Z
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.