juicysms.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 72 days left8 years old
90
juicysms.com was registered on 15 Apr 2018 via NameCheap, Inc. and the registry expiry is 15 Apr 2035. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/juicysms.com.
juicysms.com publishes 2 nameservers. DNSSEC is not signed.
juicysms.com has 2 IPv4 addresses (172.66.40.140, 172.66.43.116) and 2 IPv6 addresses (2606:4700:3108::ac42:288c, 2606:4700:3108::ac42:2b74). The geolocation database places 172.66.40.140 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 72 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS, HTTP/3, Inertia.js and Vue.js. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for juicysms.com in the checks that ran.
Domain · RDAP/WHOIS
juicysms.com was registered on 15 Apr 2018 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/juicysms.com.
| Registered | since 15 Apr 2018 |
|---|---|
| Created | 15 April 2018 |
| Updated | 1 February 2026 |
| Expires | 15 April 2035 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | macy.ns.cloudflare.com, randy.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/juicysms.com |
juicysms.com 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 macy.ns.cloudflare.com is published for juicysms.com in the registration record from https://rdap.verisign.com/com/v1/domain/juicysms.com.
Nameserver randy.ns.cloudflare.com is published for juicysms.com in the registration record from https://rdap.verisign.com/com/v1/domain/juicysms.com.
DNS
juicysms.com has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 172.66.40.140, 172.66.43.116 |
|---|---|
| AAAA | 2606:4700:3108::ac42:288c, 2606:4700:3108::ac42:2b74 |
| NS | macy.ns.cloudflare.com, randy.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.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 juicysms.com is "v=spf1 a mx ip4:185.104.29.0/24 ip4:104.27.186.55 ip4:185.104.29.84 ip6:2a06:2ec0:1:0:0:0:0:120 ip4:185.220.172.0/24 include:_spf.google.com ~all".
The DMARC text record at _dmarc.juicysms.com is "v=DMARC1; p=none; sp=none;".
IPv4 address 172.66.40.140 answers for juicysms.com at resolver 1.1.1.1:53.
IPv4 address 172.66.43.116 answers for juicysms.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3108::ac42:288c answers for juicysms.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3108::ac42:2b74 answers for juicysms.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
juicysms.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 172.66.40.140 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for juicysms.com is valid, with 72 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | juicysms.com |
| Valid from | 13 October 2026 |
| Valid until | 11 January 2027 |
| Days left | 72 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: juicysms.com.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Cloudflare · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
- Inertia.js · JavaScript frameworks
- Vue.js · JavaScript frameworks
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Inertia.js is filed under JavaScript frameworks.
Vue.js is filed under JavaScript frameworks.
On-page checks
The homepage returned HTTP 200 in 70 ms. The target title is 47 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 70 ms |
| Title length | 47 yes |
| Quoted title | "JuicySMS - The leading SMS verification service" |
| Meta description | "JuicySMS offers temporary US, UK, Dutch, and Philippine phone numbers for SMS verification. Get instant SMS codes for online services at low prices, and pay only when the code is delivered. Perfect for maintaining your privacy and security." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://juicysms.com |
| Language | en |
| Links | 72 |
| Images | 34 |
| 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 juicysms.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 | yes |
| 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 10 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
First checked on 30 October 2026; changes will appear here.
Questions
Is juicysms.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 juicysms.com?
juicysms.com is placed in Toronto, Canada.
When does juicysms.com expire?
juicysms.com expires on 15 April 2035 according to https://rdap.verisign.com/com/v1/domain/juicysms.com.
Who owns juicysms.com?
The registry did not return a person or a company for juicysms.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/juicysms.com at 2026-10-30T14:00:17Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:00:17Z
- TLS source tls:443 at 2026-10-30T14:00:17Z
- HTTP source https://juicysms.com/ at 2026-10-30T14:00:17Z
- Tech source wappalyzergo at 2026-10-30T14:00:17Z
- Geo source db-ip at 2026-10-30T14:00:17Z
- Safety source family DNS and local lists at 2026-10-30T14:00:17Z
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.