javdaddy.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 62 days left5 years oldTranco #311823
60
javdaddy.com was registered on 6 Sep 2021 via GoDaddy.com, LLC and the registry expiry is 6 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/javdaddy.com.
javdaddy.com publishes 3 nameservers. DNSSEC is not signed.
javdaddy.com has 1 IPv4 address (109.206.182.76). The geolocation database places 109.206.182.76 in Amsterdam, The Netherlands.
The TLS certificate from YE1 is valid and has 62 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Nginx. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
javdaddy.com was registered on 6 Sep 2021 via GoDaddy.com, LLC. The registry returned 4 status values and 3 nameservers from https://rdap.verisign.com/com/v1/domain/javdaddy.com.
| Registered | since 6 Sep 2021 |
|---|---|
| Created | 6 September 2021 |
| Updated | 5 August 2026 |
| Expires | 6 September 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns1.javdaddy.com, ns2.javdaddy.com, ns3.javdaddy.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/javdaddy.com |
javdaddy.com 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.
javdaddy.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
javdaddy.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.
javdaddy.com 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.
Nameserver ns1.javdaddy.com is published for javdaddy.com in the registration record from https://rdap.verisign.com/com/v1/domain/javdaddy.com.
Nameserver ns2.javdaddy.com is published for javdaddy.com in the registration record from https://rdap.verisign.com/com/v1/domain/javdaddy.com.
Nameserver ns3.javdaddy.com is published for javdaddy.com in the registration record from https://rdap.verisign.com/com/v1/domain/javdaddy.com.
DNS
javdaddy.com has 1 address record, 6 mail exchangers and 3 nameservers, measured at 1.1.1.1:53.
| A | 109.206.182.76 |
|---|---|
| AAAA | — |
| NS | ns1.javdaddy.com, ns2.javdaddy.com, ns3.javdaddy.com |
| 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, javdaddy.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at javdaddy.com is "v=spf1 include:_spf.google.com -all".
IPv4 address 109.206.182.76 answers for javdaddy.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.
Mail exchanger javdaddy.com has preference 10.
Hosting and geo
javdaddy.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 109.206.182.76 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for javdaddy.com is valid, with 62 days left and 4 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | javdaddy.com |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 62 |
| SAN count | 4 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: direct.javdaddy.com, javdaddy.com, thumbs.javdaddy.com, www.javdaddy.com.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- Nginx · Web servers, Reverse proxies
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 17 ms. The target title is 58 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 17 ms |
| Title length | 58 yes |
| Quoted title | "Japanese Porn Videos, Asian Sex Movies Tube - JavDaddy.com" |
| Meta description | "Japanese uncensored and censored videos. A large number of studio and amateur asian porn videos. Watch online for free and in high quality." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://javdaddy.com/ |
| Language | en |
| Links | 327 |
| Images | 120 |
| 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 javdaddy.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for javdaddy.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 5 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: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is javdaddy.com safe?
Cloudflare family DNS returned a block for javdaddy.com. That resolver covers adult and malware names.
Who hosts javdaddy.com?
javdaddy.com is placed in Amsterdam, The Netherlands.
When does javdaddy.com expire?
javdaddy.com expires on 6 September 2027 according to https://rdap.verisign.com/com/v1/domain/javdaddy.com.
Who owns javdaddy.com?
The registry did not return a person or a company for javdaddy.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/javdaddy.com at 2026-10-30T13:59:44Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:59:44Z
- TLS source tls:443 at 2026-10-30T13:59:44Z
- HTTP source https://javdaddy.com/ at 2026-10-30T13:59:44Z
- Tech source wappalyzergo at 2026-10-30T13:59:44Z
- Geo source db-ip at 2026-10-30T13:59:44Z
- Safety source family DNS and local lists at 2026-10-30T13:59:44Z
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.