blacklistalliance.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 30 days left9 years old
95
blacklistalliance.com was registered on 13 Mar 2017 via Amazon Registrar, Inc. and the registry expiry is 13 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/blacklistalliance.com.
blacklistalliance.com publishes 4 nameservers. DNSSEC is signed.
blacklistalliance.com has 1 IPv4 address (198.202.211.1). The geolocation database places 198.202.211.1 in San Francisco (South of Market), United States.
The TLS certificate from WE1 is valid and has 30 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Font API, Google Hosted Libraries, Google Tag Manager, HSTS, HTTP/3, Webflow, Wistia and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for blacklistalliance.com in the checks that ran.
Domain · RDAP/WHOIS
blacklistalliance.com was registered on 13 Mar 2017 via Amazon Registrar, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/blacklistalliance.com.
| Registered | since 13 Mar 2017 |
|---|---|
| Created | 13 March 2017 |
| Updated | 15 May 2026 |
| Expires | 13 March 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns-1324.awsdns-37.org, ns-1854.awsdns-39.co.uk, ns-505.awsdns-63.com, ns-578.awsdns-08.net |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/blacklistalliance.com |
blacklistalliance.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-1324.awsdns-37.org is published for blacklistalliance.com in the registration record from https://rdap.verisign.com/com/v1/domain/blacklistalliance.com.
Nameserver ns-1854.awsdns-39.co.uk is published for blacklistalliance.com in the registration record from https://rdap.verisign.com/com/v1/domain/blacklistalliance.com.
Nameserver ns-505.awsdns-63.com is published for blacklistalliance.com in the registration record from https://rdap.verisign.com/com/v1/domain/blacklistalliance.com.
Nameserver ns-578.awsdns-08.net is published for blacklistalliance.com in the registration record from https://rdap.verisign.com/com/v1/domain/blacklistalliance.com.
DNS
blacklistalliance.com has 1 address record, 5 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 198.202.211.1 |
|---|---|
| AAAA | — |
| NS | ns-1324.awsdns-37.org, ns-1854.awsdns-39.co.uk, ns-505.awsdns-63.com, ns-578.awsdns-08.net |
| 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 | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at blacklistalliance.com is "v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:45892226.spf08.hubspotemail.net mx ~all".
The DMARC text record at _dmarc.blacklistalliance.com is "v=DMARC1;p=reject;adkim=r;aspf=r;pct=100;".
IPv4 address 198.202.211.1 answers for blacklistalliance.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
blacklistalliance.com is placed in San Francisco (South of Market), United States by the local geolocation database (db-ip).
| Address | 198.202.211.1 |
|---|---|
| Country | United States |
| City | San Francisco (South of Market) |
| Source | db-ip |
SSL/TLS
The certificate for blacklistalliance.com is valid, with 30 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | blacklistalliance.com |
| Valid from | 1 September 2026 |
| Valid until | 30 November 2026 |
| Days left | 30 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: blacklistalliance.com.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Font API · Font scripts
- Google Hosted Libraries · CDN
- Google Tag Manager · Tag managers
- HSTS · Security
- HTTP/3 · Miscellaneous
- Webflow · Page builders, CMS
- Wistia · Video players
- jQuery · JavaScript libraries
Cloudflare is filed under CDN.
Google Font API is filed under Font scripts.
Google Hosted Libraries is filed under CDN.
Google Tag Manager is filed under Tag managers.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Webflow is filed under Page builders, CMS.
Wistia is filed under Video players.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 77 ms. The target title is 48 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 77 ms |
| Title length | 48 yes |
| Quoted title | "TCPA Litigation Defense — The Blacklist Alliance" |
| Meta description | "Reduce the risk of predatory TCPA litigation with comprehensive compliance, TCPA Compliance, and TCPA risk management solutions for the lead generation industry" yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://www.blacklistalliance.com/ |
| Language | — |
| Links | 48 |
| Images | 21 |
| 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 blacklistalliance.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 | yes |
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 15 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: geo city changed from empty to San Francisco (South of Market).
- October 2026: geo country changed from empty to United States.
Questions
Is blacklistalliance.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 blacklistalliance.com?
blacklistalliance.com is placed in San Francisco (South of Market), United States.
When does blacklistalliance.com expire?
blacklistalliance.com expires on 13 March 2027 according to https://rdap.verisign.com/com/v1/domain/blacklistalliance.com.
Who owns blacklistalliance.com?
The registry did not return a person or a company for blacklistalliance.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/blacklistalliance.com at 2026-10-30T13:47:21Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:21Z
- TLS source tls:443 at 2026-10-30T13:47:21Z
- HTTP source https://blacklistalliance.com/ at 2026-10-30T13:47:21Z
- Tech source wappalyzergo at 2026-10-30T13:47:21Z
- Geo source db-ip at 2026-10-30T13:47:21Z
- Safety source family DNS and local lists at 2026-10-30T13:47:21Z
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.