signal.org
We found 89 subdomains of signal.org in certificate transparency logs, passive DNS and DNS brute force; 56 resolve right now, including login.signal.org, status.signal.org and support.signal.org. signal.org is registered with MarkMonitor Inc. since 2001-04-15 and expires 2028-04-15. Its SSL certificate from Google Trust Services expires in 56 days. For email it has an SPF record, DMARC set to quarantine and DKIM keys on 1 common selector.
- Registration
- MarkMonitor Inc.Since 2001-04-15 · expires 2028-04-15
- SSL certificate
- 56 days leftGoogle Trust Services
- Subdomains
- 56 live89 discovered in total
- Email authentication
- SPF, DMARC, DKIMDMARC policy: quarantine
DNS records
6 of 7 types| A2 |
|
| AAAA2 |
|
| MX5 |
|
| TXT5 |
|
| NS2 |
|
| CAA | No CAA records |
| SOA1 |
|
Live lookup, cached up to 5 min.
WHOIS / RDAP
via rdap.org- Registrar
- MarkMonitor Inc.
- Registered
- 2001-04-15
- Expires
- 2028-04-15
- Last updated
- 2026-08-12
- Nameservers
- casey.ns.cloudflare.comzita.ns.cloudflare.com
- Status
- client delete prohibitedserver delete prohibitedclient transfer prohibitedserver transfer prohibitedclient update prohibitedserver update prohibited
RDAP with port-43 WHOIS fallback, cached up to 1 h.
SSL certificate
Valid, 56 days left- Issuer
- Google Trust ServicesCN=WE1,O=Google Trust Services,C=US
- Subject
- signal.org
- Valid from
- 2026-09-04 16:58 UTC
- Valid until
- 2026-12-03 17:58 UTC
- Serial number
- 149093019557817850531507839900410169738
- Names covered (1)
- signal.org
Live TLS handshake on port 443, cached up to 6 h.
Subdomains
56 live · 89 discovered- audit.kt.signal.org100.49.177.63
- audit.kt.staging.signal.org100.28.73.133
- build-artifacts.signal.org104.18.10.47
- cdn-ca.signal.org3.162.112.16
- cdn-staging.signal.org18.160.10.129
- cdn.signal.org18.160.18.106
- cdn2-staging.signal.org104.18.10.47
- cdn2.signal.org104.18.10.47
- cdn3-staging.signal.org104.18.10.47
- cdn3.signal.org104.18.10.47
- cdsi.reflector.signal.org40.122.45.194
- cdsi.signal.org40.122.45.194
- cdsi.staging.reflector.signal.org104.43.162.137
- cdsi.staging.signal.org104.43.162.137
- chat.reflector.signal.org13.248.212.111
- chat.signal.org13.248.212.111
- chat.staging.reflector.signal.org13.248.206.115
- chat.staging.signal.org13.248.206.115
- contentproxy.signal.org107.178.250.75
- donations.api.signal.org100.59.107.205
- donations.api.staging.signal.org100.59.107.205
- ech-chat.signal.org104.18.2.22
- ech-chat.staging.signal.org104.18.12.158
- internal.signal.org172.253.124.121
- kt.signal.org3.224.206.126
- kt.staging.signal.org100.63.69.252
- login.signal.org104.18.10.47
- mta-sts.signal.org104.18.10.47
- registration.signal.org34.111.52.112
- registration.staging.signal.org34.160.133.95
- science.signal.org216.239.32.21
- sfu.staging.test.voip.signal.org34.111.51.2
- sfu.staging.voip.signal.org35.186.225.168
- sfu.test.voip.signal.org34.160.199.171
- sfu.voip.signal.org34.117.136.13
- shop.signal.org23.227.38.74
- signal.org104.18.10.47
- status-staging.signal.org104.18.10.47
- status.signal.org104.18.10.47
- storage-manager-staging.signal.org104.18.10.47
- storage-manager.signal.org104.18.10.47
- storage-staging.signal.org172.253.124.121
- storage.signal.org172.253.124.121
- support.signal.org216.198.53.6
- svr2.reflector.signal.org20.119.62.85
- svr2.signal.org20.119.62.85
- svr2.staging.reflector.signal.org20.127.86.118
- svr2.staging.signal.org20.127.86.118
- svrb.reflector.signal.org20.232.191.209
- svrb.signal.org20.232.191.209
- svrb.staging.reflector.signal.org172.178.57.240
- updates.signal.org104.18.2.166
- updates2.signal.org104.18.26.44
- uptime.signal.org127.0.0.1
- verification.mail.signal.org104.18.10.47
- www.signal.org104.18.10.47
No subdomains found.
33 more seen in CT logs and passive DNS that don't resolve now
- api-staging.backup.signal.org
- api.backup.signal.org
- api.signal.org
- backend1.svr3.reflector.signal.org
- backend1.svr3.staging.reflector.signal.org
- backend1.svr3.staging.signal.org
- backend2.svr3.reflector.signal.org
- backend2.svr3.signal.org
- backend2.svr3.staging.reflector.signal.org
- backend2.svr3.staging.signal.org
- backend3.svr3.reflector.signal.org
- backend3.svr3.signal.org
- backend3.svr3.staging.reflector.signal.org
- backend3.svr3.staging.signal.org
- braintree.api.signal.org
- braintree.api.staging.signal.org
- call.signal.org
- calls.signal.org
- cdsh.signal.org
- desktop.build.internal.signal.org
- gcp.sfu.dev.voip.signal.org
- group.signal.org
- lpdates2.signal.org
- s2.signal.org
- status-test.signal.org
- stripe.api.signal.org
- stripe.api.staging.signal.org
- turn3.signal.org
- turn3.test.voip.signal.org
- turn3.voip.signal.org
- ud-chat.signal.org
- uploaderdemo.signal.org
- uploaderdemo2.signal.org
From CT logs, passive DNS (25+ sources) and brute-force. Live means it resolves now.
Email security
Show public keys
DKIM checked on 29 common selectors; custom ones can't be discovered. Cached up to 1 h.
Got an email from signal.org asking you to change bank details? Check it before you pay
Get this report as JSON
One call returns everything on this page. Each section is also its own endpoint.
curl "https://domain-intelligence-api.p.rapidapi.com/lookup/signal.org" \
-H "X-RapidAPI-Host: domain-intelligence-api.p.rapidapi.com" \
-H "X-RapidAPI-Key: YOUR_RAPIDAPI_KEY"
import requests
r = requests.get(
"https://domain-intelligence-api.p.rapidapi.com/lookup/signal.org",
headers={
"X-RapidAPI-Host": "domain-intelligence-api.p.rapidapi.com",
"X-RapidAPI-Key": "YOUR_RAPIDAPI_KEY",
},
timeout=30,
)
print(r.json())
// Node 18+ (built-in fetch)
const res = await fetch(
"https://domain-intelligence-api.p.rapidapi.com/lookup/signal.org",
{ headers: {
"X-RapidAPI-Host": "domain-intelligence-api.p.rapidapi.com",
"X-RapidAPI-Key": "YOUR_RAPIDAPI_KEY",
} }
);
console.log(await res.json());
<?php
$ch = curl_init("https://domain-intelligence-api.p.rapidapi.com/lookup/signal.org");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
"X-RapidAPI-Host: domain-intelligence-api.p.rapidapi.com",
"X-RapidAPI-Key: YOUR_RAPIDAPI_KEY",
]);
$data = json_decode(curl_exec($ch), true);
print_r($data);
?wait=1 waits for every subdomain source to finish