warungjav.cc

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

OfflineSafeUnder 1 year old

One re-check per domain each UTC day.

30

warungjav.cc was registered on 27 Oct 2026 via GoDaddy.com, LLC and the registry expiry is 27 Oct 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/warungjav.cc.

warungjav.cc publishes 2 nameservers. DNSSEC is not signed.

warungjav.cc has 1 IPv4 address (103.224.182.212). The geolocation database places 103.224.182.212 in San Diego, United States.

No safety warning was recorded for warungjav.cc in the checks that ran.

Domain · RDAP/WHOIS

warungjav.cc was registered on 27 Oct 2026 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/warungjav.cc.

Registeredsince 27 Oct 2026
Created27 October 2026
Updated27 October 2026
Expires27 October 2027
RegistrarGoDaddy.com, LLC
Statusclient delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Nameserversns15.abovedomains.com, ns16.abovedomains.com
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/warungjav.cc

warungjav.cc 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.

warungjav.cc 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.

warungjav.cc 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.

warungjav.cc 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 ns15.abovedomains.com is published for warungjav.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/warungjav.cc.

Nameserver ns16.abovedomains.com is published for warungjav.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/warungjav.cc.

DNS

warungjav.cc has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A103.224.182.212
AAAA—
NSns15.abovedomains.com, ns16.abovedomains.com
MXpark-mx.above.com (10)
SPFpresent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at warungjav.cc is "v=spf1 ip6:fdcf:abda:4154::/48 -all".

IPv4 address 103.224.182.212 answers for warungjav.cc at resolver 1.1.1.1:53.

Mail exchanger park-mx.above.com has preference 10.

A random label under warungjav.cc also resolved, which means wildcard DNS is on.

Hosting and geo

warungjav.cc is placed in San Diego, United States by the local geolocation database (db-ip).

Address103.224.182.212
CountryUnited States
CitySan Diego
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

No TLS certificate was read for warungjav.cc on port 443.

Availableno
Sourcetls:443

dial tcp 103.224.182.212:443: i/o timeout

Tech stack

Tech detection did not run.

Checkedno
Sourcewappalyzergo

On-page checks

The homepage fetch did not return a status code.

Statusnone

context deadline exceeded

Security

Family DNS for warungjav.cc is clear, and URLhaus is clear. Source: family DNS and local lists.

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

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 0 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 0 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 0 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: geo city changed from empty to San Diego.
  • October 2026: geo country changed from empty to United States.

Questions

Is warungjav.cc 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 warungjav.cc?

warungjav.cc is placed in San Diego, United States.

When does warungjav.cc expire?

warungjav.cc expires on 27 October 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/warungjav.cc.

Who owns warungjav.cc?

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

Sources

  • RDAP source https://tld-rdap.verisign.com/cc/v1/domain/warungjav.cc at 2026-10-30T13:35:53Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:35:53Z
  • TLS source tls:443 at 2026-10-30T13:35:53Z
  • HTTP source https://warungjav.cc/ at 2026-10-30T13:35:53Z
  • Tech source not available at 2026-10-30T13:35:53Z
  • Geo source db-ip at 2026-10-30T13:35:53Z
  • Safety source family DNS and local lists at 2026-10-30T13:35:53Z

Methodology

Related reports

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

.cc GoDaddy.com, 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.