joinsequence.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 178 days left4 years oldTranco #109074
80
joinsequence.com was registered on 17 Nov 2021 via GoDaddy Corporate Domains, LLC and the registry expiry is 17 Nov 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/joinsequence.com.
joinsequence.com publishes 4 nameservers. DNSSEC is not signed.
joinsequence.com has 4 IPv4 addresses (3.160.150.110, 3.160.150.49, 3.160.150.71, 3.160.150.96). The geolocation database places 3.160.150.110 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 178 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Google Analytics, HSTS, Varnish and Vercel. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for joinsequence.com in the checks that ran.
Domain · RDAP/WHOIS
joinsequence.com was registered on 17 Nov 2021 via GoDaddy Corporate Domains, LLC. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/joinsequence.com.
| Registered | since 17 Nov 2021 |
|---|---|
| Created | 17 November 2021 |
| Updated | 18 October 2026 |
| Expires | 17 November 2027 |
| Registrar | GoDaddy Corporate Domains, LLC |
| Status | client transfer prohibited |
| Nameservers | ns-1408.awsdns-48.org, ns-1578.awsdns-05.co.uk, ns-341.awsdns-42.com, ns-892.awsdns-47.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/joinsequence.com |
joinsequence.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 ns-1408.awsdns-48.org is published for joinsequence.com in the registration record from https://rdap.verisign.com/com/v1/domain/joinsequence.com.
Nameserver ns-1578.awsdns-05.co.uk is published for joinsequence.com in the registration record from https://rdap.verisign.com/com/v1/domain/joinsequence.com.
Nameserver ns-341.awsdns-42.com is published for joinsequence.com in the registration record from https://rdap.verisign.com/com/v1/domain/joinsequence.com.
Nameserver ns-892.awsdns-47.net is published for joinsequence.com in the registration record from https://rdap.verisign.com/com/v1/domain/joinsequence.com.
DNS
joinsequence.com has 4 address records, 4 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 3.160.150.110, 3.160.150.49, 3.160.150.71, 3.160.150.96 |
|---|---|
| AAAA | — |
| NS | ns-1408.awsdns-48.org, ns-1578.awsdns-05.co.uk, ns-341.awsdns-42.com, ns-892.awsdns-47.net |
| MX | mxa-0000eb02.gslb.pphosted.com (10) Proofpoint, mxb-0000eb02.gslb.pphosted.com (10) Proofpoint, mx0a-0000eb02.pphosted.com (20) Proofpoint, mx0b-0000eb02.pphosted.com (20) Proofpoint |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at joinsequence.com is "v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all".
The DMARC text record at _dmarc.joinsequence.com is "v=DMARC1; p=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]".
IPv4 address 3.160.150.110 answers for joinsequence.com at resolver 1.1.1.1:53.
IPv4 address 3.160.150.49 answers for joinsequence.com at resolver 1.1.1.1:53.
IPv4 address 3.160.150.71 answers for joinsequence.com at resolver 1.1.1.1:53.
IPv4 address 3.160.150.96 answers for joinsequence.com at resolver 1.1.1.1:53.
Mail exchanger mxa-0000eb02.gslb.pphosted.com has preference 10. The host is recognised as Proofpoint.
Mail exchanger mxb-0000eb02.gslb.pphosted.com has preference 10. The host is recognised as Proofpoint.
Mail exchanger mx0a-0000eb02.pphosted.com has preference 20. The host is recognised as Proofpoint.
Mail exchanger mx0b-0000eb02.pphosted.com has preference 20. The host is recognised as Proofpoint.
Hosting and geo
joinsequence.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 3.160.150.110 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for joinsequence.com is valid, with 178 days left and 7 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | app.joinsequence.com |
| Valid from | 12 October 2026 |
| Valid until | 27 April 2027 |
| Days left | 178 |
| SAN count | 7 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: app.joinsequence.com, bedrock.weekendhealth.com, joinsequence.com, member.joinsequence.com, webhooks-listener.weekendhealth.com, ww-integration-api.joinsequence.com, www.joinsequence.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Google Analytics · Analytics
- HSTS · Security
- Varnish · Caching
- Vercel · PaaS
Google Analytics is filed under Analytics.
HSTS is filed under Security.
Varnish is filed under Caching.
Vercel is filed under PaaS.
On-page checks
The homepage returned HTTP 200 in 6 ms. The target title is 59 characters and the page has 3 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 6 ms |
| Title length | 59 yes |
| Quoted title | "Online Prescription Weight-Loss Medication | WeightWatchers" |
| Meta description | "Access online weight-loss medication for as low as $25/first month. Our doctors and clinicians are with you every step of the journey." yes |
| H1 count | 3 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | https://www.weightwatchers.com/us/weight-loss-medication |
| Language | en |
| Links | 56 |
| Images | 26 |
| 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 joinsequence.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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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 joinsequence.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 joinsequence.com?
joinsequence.com is placed in Frankfurt am Main, Germany.
When does joinsequence.com expire?
joinsequence.com expires on 17 November 2027 according to https://rdap.verisign.com/com/v1/domain/joinsequence.com.
Who owns joinsequence.com?
The registry did not return a person or a company for joinsequence.com. RDAP often redacts the registrant. The registrar on file is GoDaddy Corporate Domains, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/joinsequence.com at 2026-10-30T14:00:12Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:00:12Z
- TLS source tls:443 at 2026-10-30T14:00:12Z
- HTTP source https://joinsequence.com/ at 2026-10-30T14:00:12Z
- Tech source wappalyzergo at 2026-10-30T14:00:12Z
- Geo source db-ip at 2026-10-30T14:00:12Z
- Safety source family DNS and local lists at 2026-10-30T14:00: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.