pianbus.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 83 days leftUnder 1 year old
47
pianbus.com was registered on 10 Jul 2026 via Dominet (HK) Limited and the registry expiry is 10 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/pianbus.com.
pianbus.com publishes 2 nameservers. DNSSEC is not signed.
pianbus.com has 3 IPv4 addresses (104.194.206.133, 146.19.114.69, 146.19.114.74). The geolocation database places 104.194.206.133 in Riverton, United States.
The TLS certificate from YR2 is valid and has 83 days left (TLS 1.2).
No safety warning was recorded for pianbus.com in the checks that ran.
Domain · RDAP/WHOIS
pianbus.com was registered on 10 Jul 2026 via Dominet (HK) Limited. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/pianbus.com.
| Registered | since 10 Jul 2026 |
|---|---|
| Created | 10 July 2026 |
| Updated | 17 October 2026 |
| Expires | 10 July 2027 |
| Registrar | Dominet (HK) Limited |
| Status | active |
| Nameservers | megan.ns.cloudflare.com, tosana.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/pianbus.com |
Nameserver megan.ns.cloudflare.com is published for pianbus.com in the registration record from https://rdap.verisign.com/com/v1/domain/pianbus.com.
Nameserver tosana.ns.cloudflare.com is published for pianbus.com in the registration record from https://rdap.verisign.com/com/v1/domain/pianbus.com.
DNS
pianbus.com has 3 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.194.206.133, 146.19.114.69, 146.19.114.74 |
|---|---|
| AAAA | — |
| NS | megan.ns.cloudflare.com, tosana.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.194.206.133 answers for pianbus.com at resolver 1.1.1.1:53.
IPv4 address 146.19.114.69 answers for pianbus.com at resolver 1.1.1.1:53.
IPv4 address 146.19.114.74 answers for pianbus.com at resolver 1.1.1.1:53.
Hosting and geo
pianbus.com is placed in Riverton, United States by the local geolocation database (db-ip).
| Address | 104.194.206.133 |
|---|---|
| Country | United States |
| City | Riverton |
| Source | db-ip |
SSL/TLS
The certificate for pianbus.com is valid, with 83 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | www.pianbus.com |
| Valid from | 24 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 83 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: pianbus.com, www.pianbus.com.
Tech stack
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
On-page checks
The homepage returned HTTP 403 in 175 ms. The target title is 13 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 175 ms |
| Title length | 13 yes |
| Quoted title | "403 Forbidden" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| 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 pianbus.com 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 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 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Riverton.
- October 2026: geo country changed from empty to United States.
Questions
Is pianbus.com 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 pianbus.com?
pianbus.com is placed in Riverton, United States.
When does pianbus.com expire?
pianbus.com expires on 10 July 2027 according to https://rdap.verisign.com/com/v1/domain/pianbus.com.
Who owns pianbus.com?
The registry did not return a person or a company for pianbus.com. RDAP often redacts the registrant. The registrar on file is Dominet (HK) Limited.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/pianbus.com at 2026-10-30T14:09:12Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:09:12Z
- TLS source tls:443 at 2026-10-30T14:09:12Z
- HTTP source https://pianbus.com/ at 2026-10-30T14:09:12Z
- Tech source wappalyzergo at 2026-10-30T14:09:12Z
- Geo source db-ip at 2026-10-30T14:09:12Z
- Safety source family DNS and local lists at 2026-10-30T14:09:12Z
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.