jizzle.com

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

Online · 200Family DNS blockedSSL: 58 days left23 years oldTranco #583525

One re-check per domain each UTC day.

60

jizzle.com was registered on 8 Oct 2003 via eNom, LLC and the registry expiry is 8 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/jizzle.com.

jizzle.com publishes 3 nameservers. DNSSEC is not signed.

jizzle.com has 14 IPv4 addresses (152.233.120.1, 152.233.120.10, 152.233.120.12, 152.233.120.13, 152.233.120.14, 152.233.120.15, 152.233.120.2, 152.233.120.3, 152.233.120.4, 152.233.120.5, 152.233.120.6, 152.233.120.7, 152.233.120.8, 152.233.120.9). The geolocation database places 152.233.120.1 in Amsterdam, The Netherlands.

The TLS certificate from YR2 is valid and has 58 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Nginx, RequireJS and jQuery. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

jizzle.com was registered on 8 Oct 2003 via eNom, LLC. The registry returned 1 status value and 3 nameservers from https://rdap.verisign.com/com/v1/domain/jizzle.com.

Registeredsince 8 Oct 2003
Created8 October 2003
Updated9 September 2026
Expires8 October 2027
RegistrareNom, LLC
Statusclient transfer prohibited
Nameserversns1.wgcz.net, ns2.wgcz.net, ns3.wgcz.net
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/jizzle.com

jizzle.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 ns1.wgcz.net is published for jizzle.com in the registration record from https://rdap.verisign.com/com/v1/domain/jizzle.com.

Nameserver ns2.wgcz.net is published for jizzle.com in the registration record from https://rdap.verisign.com/com/v1/domain/jizzle.com.

Nameserver ns3.wgcz.net is published for jizzle.com in the registration record from https://rdap.verisign.com/com/v1/domain/jizzle.com.

DNS

jizzle.com has 14 address records, 1 mail exchanger and 3 nameservers, measured at 1.1.1.1:53.

A152.233.120.1, 152.233.120.10, 152.233.120.12, 152.233.120.13, 152.233.120.14, 152.233.120.15, 152.233.120.2, 152.233.120.3, 152.233.120.4, 152.233.120.5, 152.233.120.6, 152.233.120.7, 152.233.120.8, 152.233.120.9
AAAA—
NSns1.wgcz.net, ns2.wgcz.net, ns3.wgcz.net
MXjizzle.com (10)
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 152.233.120.1 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.10 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.12 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.13 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.14 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.15 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.2 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.3 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.4 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.5 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.6 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.7 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.8 answers for jizzle.com at resolver 1.1.1.1:53.

IPv4 address 152.233.120.9 answers for jizzle.com at resolver 1.1.1.1:53.

Mail exchanger jizzle.com has preference 10.

A random label under jizzle.com also resolved, which means wildcard DNS is on.

Hosting and geo

jizzle.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).

Address152.233.120.1
CountryThe Netherlands
CityAmsterdam
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for jizzle.com is valid, with 58 days left and 2 subject alternative names. Source: tls:443.

IssuerYR2
Subject*.jizzle.com
Valid from30 September 2026
Valid until29 December 2026
Days left58
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.jizzle.com, jizzle.com.

Tech stack

Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.

  • Nginx · Web servers, Reverse proxies
  • RequireJS · JavaScript frameworks
  • jQuery · JavaScript libraries

Nginx is filed under Web servers, Reverse proxies.

RequireJS is filed under JavaScript frameworks.

jQuery is filed under JavaScript libraries.

On-page checks

The homepage returned HTTP 200 in 59 ms. The target title is 51 characters and the page has 1 H1 heading.

Status200
TTFB59 ms
Title length51 yes
Quoted title"Jizz, Facial Cumshot, Creampie videos at JIZZLE.COM"
Meta descriptionnone no
H1 count1
HSTSno no
CSPyes
X-Frame-OptionsSAMEORIGIN
Robots meta—
Canonical—
Languageen
Links291
Images211
Faviconyes

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 jizzle.com 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
CSPyes

Cloudflare family DNS returned a block for jizzle.com. 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 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 10 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: geo city changed from empty to Amsterdam.
  • October 2026: geo country changed from empty to The Netherlands.

Questions

Is jizzle.com safe?

Cloudflare family DNS returned a block for jizzle.com. That resolver covers adult and malware names.

Who hosts jizzle.com?

jizzle.com is placed in Amsterdam, The Netherlands.

When does jizzle.com expire?

jizzle.com expires on 8 October 2027 according to https://rdap.verisign.com/com/v1/domain/jizzle.com.

Who owns jizzle.com?

The registry did not return a person or a company for jizzle.com. RDAP often redacts the registrant. The registrar on file is eNom, LLC.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/jizzle.com at 2026-10-30T14:00:03Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:00:03Z
  • TLS source tls:443 at 2026-10-30T14:00:03Z
  • HTTP source https://jizzle.com/ at 2026-10-30T14:00:03Z
  • Tech source wappalyzergo at 2026-10-30T14:00:03Z
  • Geo source db-ip at 2026-10-30T14:00:03Z
  • Safety source family DNS and local lists at 2026-10-30T14:00:03Z

Methodology

Related reports

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

.com eNom, LLC

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.