buffstreams.app
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
30
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
30
buffstreams.app was registered on 13 Nov 2021 via MarkMonitor Inc. and the registry expiry is 13 Nov 2028. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/buffstreams.app.
buffstreams.app publishes 2 nameservers. DNSSEC is not signed.
buffstreams.app has 1 IPv4 address (54.235.210.28). The geolocation database places 54.235.210.28 in Ashburn, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
No safety warning was recorded for buffstreams.app in the checks that ran.
buffstreams.app was registered on 13 Nov 2021 via MarkMonitor Inc.. The registry returned 6 status values and 2 nameservers from https://pubapi.registry.google/rdap/domain/buffstreams.app.
| Registered | since 13 Nov 2021 |
|---|---|
| Created | 13 November 2021 |
| Updated | 10 July 2026 |
| Expires | 13 November 2028 |
| Registrar | MarkMonitor Inc. |
| Status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
| Nameservers | ns1.seizedservers.com, ns2.seizedservers.com |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/buffstreams.app |
buffstreams.app 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.
buffstreams.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.
buffstreams.app 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.
buffstreams.app carries the status "server delete prohibited". The registry itself is refusing deletes. This lock is not one the registrar can clear alone.
buffstreams.app carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
buffstreams.app carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
Nameserver ns1.seizedservers.com is published for buffstreams.app in the registration record from https://pubapi.registry.google/rdap/domain/buffstreams.app.
Nameserver ns2.seizedservers.com is published for buffstreams.app in the registration record from https://pubapi.registry.google/rdap/domain/buffstreams.app.
buffstreams.app has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 54.235.210.28 |
|---|---|
| AAAA | — |
| NS | ns1.seizedservers.com, ns2.seizedservers.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 54.235.210.28 answers for buffstreams.app at resolver 1.1.1.1:53.
A random label under buffstreams.app also resolved, which means wildcard DNS is on.
buffstreams.app is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 54.235.210.28 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
The certificate for buffstreams.app is not valid, with -18 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | buffstreams.app |
| Valid from | 14 July 2026 |
| Valid until | 12 October 2026 |
| Days left | -18 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: buffstreams.app.
Validation result: certificate did not validate
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://buffstreams.app/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T13:31:23Z is after 2026-10-12T14:13:33Z
Family DNS for buffstreams.app 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.
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 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 5 of 5. Five points at one year, two points at 30 days.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
buffstreams.app is placed in Ashburn, United States.
buffstreams.app expires on 13 November 2028 according to https://pubapi.registry.google/rdap/domain/buffstreams.app.
The registry did not return a person or a company for buffstreams.app. RDAP often redacts the registrant. The registrar on file is MarkMonitor Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.