onbuka.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 128 days left5 years old
80
onbuka.com was registered on 3 Jun 2021 via Alibaba Cloud Computing (Beijing) Co., Ltd. and the registry expiry is 3 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/onbuka.com.
onbuka.com publishes 2 nameservers. DNSSEC is not signed.
onbuka.com has 4 IPv4 addresses (18.239.50.128, 18.239.50.18, 18.239.50.25, 18.239.50.52). The geolocation database places 18.239.50.128 in Amsterdam, The Netherlands.
The TLS certificate from Amazon RSA 2048 M01 is valid and has 128 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon Web Services, Google Tag Manager, HTTP/3, Nginx, Swiper and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for onbuka.com in the checks that ran.
Domain · RDAP/WHOIS
onbuka.com was registered on 3 Jun 2021 via Alibaba Cloud Computing (Beijing) Co., Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/onbuka.com.
| Registered | since 3 Jun 2021 |
|---|---|
| Created | 3 June 2021 |
| Updated | 15 July 2025 |
| Expires | 3 June 2027 |
| Registrar | Alibaba Cloud Computing (Beijing) Co., Ltd. |
| Status | active |
| Nameservers | bailey.ns.cloudflare.com, kolton.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/onbuka.com |
Nameserver bailey.ns.cloudflare.com is published for onbuka.com in the registration record from https://rdap.verisign.com/com/v1/domain/onbuka.com.
Nameserver kolton.ns.cloudflare.com is published for onbuka.com in the registration record from https://rdap.verisign.com/com/v1/domain/onbuka.com.
DNS
onbuka.com has 4 address records, 4 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 18.239.50.128, 18.239.50.18, 18.239.50.25, 18.239.50.52 |
|---|---|
| AAAA | — |
| NS | bailey.ns.cloudflare.com, kolton.ns.cloudflare.com |
| MX | qiye163mx01.mxmail.netease.com (5), qiye163mx02.mxmail.netease.com (5), qiye163mx01.mxmail.netease.com (10), qiye163mx02.mxmail.netease.com (10) |
| SPF | present |
| DMARC | present |
| CAA | issue amazon.com, issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild amazon.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at onbuka.com is "v=spf1 include:spf.163.com -all".
The DMARC text record at _dmarc.onbuka.com is "v=DMARC1; p=none; fo=1; ruf=mailto:[email protected]; rua=mailto:[email protected]".
IPv4 address 18.239.50.128 answers for onbuka.com at resolver 1.1.1.1:53.
IPv4 address 18.239.50.18 answers for onbuka.com at resolver 1.1.1.1:53.
IPv4 address 18.239.50.25 answers for onbuka.com at resolver 1.1.1.1:53.
IPv4 address 18.239.50.52 answers for onbuka.com at resolver 1.1.1.1:53.
Mail exchanger qiye163mx01.mxmail.netease.com has preference 5.
Mail exchanger qiye163mx02.mxmail.netease.com has preference 5.
Mail exchanger qiye163mx01.mxmail.netease.com has preference 10.
Mail exchanger qiye163mx02.mxmail.netease.com has preference 10.
Hosting and geo
onbuka.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 18.239.50.128 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for onbuka.com is valid, with 128 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M01 |
|---|---|
| Subject | onbuka.com |
| Valid from | 23 August 2026 |
| Valid until | 8 March 2027 |
| Days left | 128 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.onbuka.com, onbuka.com.
Tech stack
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
- Amazon CloudFront · CDN
- Amazon Web Services · PaaS
- Google Tag Manager · Tag managers
- HTTP/3 · Miscellaneous
- Nginx · Web servers, Reverse proxies
- Swiper · JavaScript libraries
- jQuery · JavaScript libraries
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
Google Tag Manager is filed under Tag managers.
HTTP/3 is filed under Miscellaneous.
Nginx is filed under Web servers, Reverse proxies.
Swiper is filed under JavaScript libraries.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 22 ms. The target title is 85 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 22 ms |
| Title length | 85 no |
| Quoted title | "SMS Service, A2P SMS, Global SMS, BUKA Cloud Communication - BUKA Cloud Communication" |
| Meta description | "BUKA cloud communication in a global SMS platform that provides global SMS,send free text message, send text message online, and SMS text services to help enterprises and individual business connect users locally and around the globe, and achieve more." yes |
| H1 count | 2 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 129 |
| Images | 215 |
| Favicon | yes |
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 onbuka.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 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 15 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: dns a changed from 18.245.60.2,18.245.60.54,18.245.60.63,18.245.60.97 to 18.239.50.128,18.239.50.18,18.239.50.25,18.239.50.52.
Questions
Is onbuka.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 onbuka.com?
onbuka.com is placed in Amsterdam, The Netherlands.
When does onbuka.com expire?
onbuka.com expires on 3 June 2027 according to https://rdap.verisign.com/com/v1/domain/onbuka.com.
Who owns onbuka.com?
The registry did not return a person or a company for onbuka.com. RDAP often redacts the registrant. The registrar on file is Alibaba Cloud Computing (Beijing) Co., Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/onbuka.com at 2026-10-30T14:07:54Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:07:54Z
- TLS source tls:443 at 2026-10-30T14:07:54Z
- HTTP source https://onbuka.com/ at 2026-10-30T14:07:54Z
- Tech source wappalyzergo at 2026-10-30T14:07:54Z
- Geo source db-ip at 2026-10-30T14:07:54Z
- Safety source family DNS and local lists at 2026-10-30T14:07:54Z
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.