synapse.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 55 days left6 years old
80
synapse.to was registered on 6 May 2020 via MarkMonitor Inc. and the registry expiry is 19 Oct 2029. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/synapse.to.
synapse.to publishes 2 nameservers. DNSSEC is not signed.
synapse.to has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 55 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for synapse.to in the checks that ran.
Domain · RDAP/WHOIS
synapse.to was registered on 6 May 2020 via MarkMonitor Inc.. The registry returned 3 status values and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/synapse.to.
| Registered | since 6 May 2020 |
|---|---|
| Created | 6 May 2020 |
| Updated | 13 January 2026 |
| Expires | 19 October 2029 |
| Registrar | MarkMonitor Inc. |
| Status | client update prohibited, client transfer prohibited, client delete prohibited |
| Nameservers | ara.ns.cloudflare.com, seth.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/synapse.to |
synapse.to 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.
synapse.to 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.
synapse.to 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.
Nameserver ara.ns.cloudflare.com is published for synapse.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/synapse.to.
Nameserver seth.ns.cloudflare.com is published for synapse.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/synapse.to.
DNS
synapse.to has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | ara.ns.cloudflare.com, seth.ns.cloudflare.com |
| MX | synapse-to.mail.protection.outlook.com (0) Microsoft 365 |
| 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 synapse.to is "v=spf1 include:spf.braintreegateway.com mx include:spf.protection.outlook.com ~all".
The DMARC text record at _dmarc.synapse.to is "v=DMARC1; p=quarantine; rua=mailto:[email protected]".
IPv4 address 188.114.96.3 answers for synapse.to at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for synapse.to at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for synapse.to at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for synapse.to at resolver 1.1.1.1:53.
Mail exchanger synapse-to.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
synapse.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for synapse.to is valid, with 55 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | synapse.to |
| Valid from | 26 September 2026 |
| Valid until | 25 December 2026 |
| Days left | 55 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: synapse.to.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 65 ms. The target title is 20 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 65 ms |
| Title length | 20 yes |
| Quoted title | "Synapse X - Goodbye!" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 2 |
| Images | 1 |
| Favicon | no |
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 synapse.to 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 aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
Questions
Is synapse.to 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 synapse.to?
synapse.to is placed in Toronto, Canada.
When does synapse.to expire?
synapse.to expires on 19 October 2029 according to https://rdap.tonicregistry.to/rdap/domain/synapse.to.
Who owns synapse.to?
The registry did not return a person or a company for synapse.to. RDAP often redacts the registrant. The registrar on file is MarkMonitor Inc..
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/synapse.to at 2026-10-30T15:18:43Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:18:43Z
- TLS source tls:443 at 2026-10-30T15:18:43Z
- HTTP source https://synapse.to/ at 2026-10-30T15:18:43Z
- Tech source wappalyzergo at 2026-10-30T15:18:43Z
- Geo source db-ip at 2026-10-30T15:18:43Z
- Safety source family DNS and local lists at 2026-10-30T15:18:43Z
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.