mmsbee.site
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 59 days left1 year old
15
mmsbee.site was registered on 31 May 2025 via Sav.com, LLC - 23 and the registry expiry is 31 May 2027. WHOIS data came from RDAP at https://rdap.radix.host/rdap/domain/mmsbee.site.
mmsbee.site publishes 2 nameservers. DNSSEC is not signed.
mmsbee.site has 3 IPv4 addresses (172.234.212.77, 172.236.103.15, 172.239.193.194). The geolocation database places 172.234.212.77 in Chicago, United States.
The TLS certificate from YE1 is not valid (TLS 1.3).
Domain · RDAP/WHOIS
mmsbee.site was registered on 31 May 2025 via Sav.com, LLC - 23. The registry returned 1 status value and 2 nameservers from https://rdap.radix.host/rdap/domain/mmsbee.site.
| Registered | since 31 May 2025 |
|---|---|
| Created | 31 May 2025 |
| Updated | 7 May 2026 |
| Expires | 31 May 2027 |
| Registrar | Sav.com, LLC - 23 |
| Status | client transfer prohibited |
| Nameservers | ns1-coming-soon.sav.com, ns2-coming-soon.sav.com |
| DNSSEC | no |
| Source | https://rdap.radix.host/rdap/domain/mmsbee.site |
mmsbee.site 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 ns1-coming-soon.sav.com is published for mmsbee.site in the registration record from https://rdap.radix.host/rdap/domain/mmsbee.site.
Nameserver ns2-coming-soon.sav.com is published for mmsbee.site in the registration record from https://rdap.radix.host/rdap/domain/mmsbee.site.
DNS
mmsbee.site has 3 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 172.234.212.77, 172.236.103.15, 172.239.193.194 |
|---|---|
| AAAA | — |
| NS | ns1-coming-soon.sav.com, ns2-coming-soon.sav.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 172.234.212.77 answers for mmsbee.site at resolver 1.1.1.1:53.
IPv4 address 172.236.103.15 answers for mmsbee.site at resolver 1.1.1.1:53.
IPv4 address 172.239.193.194 answers for mmsbee.site at resolver 1.1.1.1:53.
A random label under mmsbee.site also resolved, which means wildcard DNS is on.
Hosting and geo
mmsbee.site is placed in Chicago, United States by the local geolocation database (db-ip).
| Address | 172.234.212.77 |
|---|---|
| Country | United States |
| City | Chicago |
| Source | db-ip |
SSL/TLS
The certificate for mmsbee.site is not valid, with 59 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | mmsbee.site |
| Valid from | 30 September 2026 |
| Valid until | 29 December 2026 |
| Days left | 59 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: mmsbee.site.
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://mmsbee.site/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for mmsbee.site 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 | no |
Cloudflare family DNS returned a block for mmsbee.site. 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 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 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
- October 2026: geo city changed from empty to Chicago.
- October 2026: geo country changed from empty to United States.
Questions
Is mmsbee.site safe?
Cloudflare family DNS returned a block for mmsbee.site. That resolver covers adult and malware names.
Who hosts mmsbee.site?
mmsbee.site is placed in Chicago, United States.
When does mmsbee.site expire?
mmsbee.site expires on 31 May 2027 according to https://rdap.radix.host/rdap/domain/mmsbee.site.
Who owns mmsbee.site?
The registry did not return a person or a company for mmsbee.site. RDAP often redacts the registrant. The registrar on file is Sav.com, LLC - 23.
Sources
- RDAP source https://rdap.radix.host/rdap/domain/mmsbee.site at 2026-10-30T15:09:30Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:09:30Z
- TLS source tls:443 at 2026-10-30T15:09:30Z
- HTTP source https://mmsbee.site/ at 2026-10-30T15:09:30Z
- Tech source not available at 2026-10-30T15:09:30Z
- Geo source db-ip at 2026-10-30T15:09:30Z
- Safety source family DNS and local lists at 2026-10-30T15:09:30Z
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.