badwap.live

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

HTTP 520Family DNS blockedSSL: 82 days left7 years oldTranco #91890

One re-check per domain each UTC day.

40

badwap.live was registered on 18 Aug 2019 via Name.com, Inc. and the registry expiry is 18 Aug 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/badwap.live.

badwap.live publishes 2 nameservers. DNSSEC is not signed.

badwap.live has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 82 days left (TLS 1.3).

Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

badwap.live was registered on 18 Aug 2019 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/badwap.live.

Registeredsince 18 Aug 2019
Created18 August 2019
Updated2 October 2026
Expires18 August 2027
RegistrarName.com, Inc.
Statusclient transfer prohibited
Nameserverspam.ns.cloudflare.com, marek.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.identitydigital.services/rdap/domain/badwap.live

badwap.live 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 pam.ns.cloudflare.com is published for badwap.live in the registration record from https://rdap.identitydigital.services/rdap/domain/badwap.live.

Nameserver marek.ns.cloudflare.com is published for badwap.live in the registration record from https://rdap.identitydigital.services/rdap/domain/badwap.live.

DNS

badwap.live has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A188.114.96.3, 188.114.97.3
AAAA2a06:98c1:3120::3, 2a06:98c1:3121::3
NSmarek.ns.cloudflare.com, pam.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 188.114.96.3 answers for badwap.live at resolver 1.1.1.1:53.

IPv4 address 188.114.97.3 answers for badwap.live at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3120::3 answers for badwap.live at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3121::3 answers for badwap.live at resolver 1.1.1.1:53.

Hosting and geo

badwap.live is placed in Toronto, Canada by the local geolocation database (db-ip).

Address188.114.96.3
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for badwap.live is valid, with 82 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectbadwap.live
Valid from23 October 2026
Valid until21 January 2027
Days left82
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.badwap.live, badwap.live.

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 520 in 57 ms. The target title is 59 characters and the page has 1 H1 heading.

Status520
TTFB57 ms
Title length59 yes
Quoted title"badwap.live | 520: Web server is returning an unknown error"
Meta descriptionnone no
H1 count1
HSTSno no
CSPno
X-Frame-OptionsSAMEORIGIN
Robots metanoindex, nofollow
Canonical—
Languageen-US
Links5
Images0
Faviconno

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 badwap.live is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for badwap.live. That resolver covers adult and malware names.

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 10 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 0 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 0 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 a changed from 188.114.96.4,188.114.97.4 to 188.114.96.3,188.114.97.3.

Questions

Is badwap.live safe?

Cloudflare family DNS returned a block for badwap.live. That resolver covers adult and malware names.

Who hosts badwap.live?

badwap.live is placed in Toronto, Canada.

When does badwap.live expire?

badwap.live expires on 18 August 2027 according to https://rdap.identitydigital.services/rdap/domain/badwap.live.

Who owns badwap.live?

The registry did not return a person or a company for badwap.live. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..

Sources

  • RDAP source https://rdap.identitydigital.services/rdap/domain/badwap.live at 2026-10-30T14:41:57Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:41:57Z
  • TLS source tls:443 at 2026-10-30T14:41:57Z
  • HTTP source https://badwap.live/ at 2026-10-30T14:41:57Z
  • Tech source wappalyzergo at 2026-10-30T14:41:57Z
  • Geo source db-ip at 2026-10-30T14:41:57Z
  • Safety source family DNS and local lists at 2026-10-30T14:41:57Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.live Name.com, Inc.

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.

Removal policy

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.