fc1adult.com

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

Online · 200Family DNS blockedSSL: 22 days left9 years oldTranco #645879

One re-check per domain each UTC day.

60

fc1adult.com was registered on 15 Jul 2017 via eNom, LLC and the registry expiry is 15 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/fc1adult.com.

fc1adult.com has 1 IPv4 address (104.244.98.228). The geolocation database places 104.244.98.228 in Las Vegas, United States.

The TLS certificate from GlobalSign GCC R6 AlphaSSL CA 2025 is valid and has 22 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Google Analytics, HSTS and Nginx. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

fc1adult.com was registered on 15 Jul 2017 via eNom, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/fc1adult.com.

Registeredsince 15 Jul 2017
Created15 July 2017
Updated11 February 2026
Expires15 July 2027
RegistrareNom, LLC
Statusclient transfer prohibited
Nameserversmdns1.fc2.com, mdns2.fc2.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/fc1adult.com

fc1adult.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 mdns1.fc2.com is published for fc1adult.com in the registration record from https://rdap.verisign.com/com/v1/domain/fc1adult.com.

Nameserver mdns2.fc2.com is published for fc1adult.com in the registration record from https://rdap.verisign.com/com/v1/domain/fc1adult.com.

DNS

fc1adult.com has 1 address record, 1 mail exchanger and 0 nameservers, measured at 1.1.1.1:53.

A104.244.98.228
AAAA—
NS—
MXmx01.fc1adult.com (10)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at fc1adult.com is "v=spf1 include:spf-hosting.fc2.com ~all".

IPv4 address 104.244.98.228 answers for fc1adult.com at resolver 1.1.1.1:53.

Mail exchanger mx01.fc1adult.com has preference 10.

Hosting and geo

fc1adult.com is placed in Las Vegas, United States by the local geolocation database (db-ip).

Address104.244.98.228
CountryUnited States
CityLas Vegas
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerGlobalSign GCC R6 AlphaSSL CA 2025
Subjectwww.fc1adult.com
Valid from8 May 2026
Valid until23 November 2026
Days left22
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: fc1adult.com, www.fc1adult.com.

Tech stack

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

  • Google Analytics · Analytics
  • HSTS · Security
  • Nginx · Web servers, Reverse proxies

Google Analytics is filed under Analytics.

HSTS is filed under Security.

Nginx is filed under Web servers, Reverse proxies.

On-page checks

The homepage returned HTTP 200 in 244 ms. The target title is 13 characters and the page has 0 H1 headings.

Status200
TTFB244 ms
Title length13 yes
Quoted title"ネットで裸を晒す女の子たち"
Meta description"画像・動画・生配信などを通して裸を晒している女の子たちを可能な限り集めて紹介しています。 - ネットで裸を晒す女の子たち" yes
H1 count0
HSTSyes yes
CSPno
X-Frame-Options—
Robots meta—
Canonicalhttps://fc1adult.com
Languageja
Links95
Images35
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 fc1adult.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
HSTSyes
CSPno

Cloudflare family DNS returned a block for fc1adult.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 Las Vegas.
  • October 2026: geo country changed from empty to United States.

Questions

Is fc1adult.com safe?

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

Who hosts fc1adult.com?

fc1adult.com is placed in Las Vegas, United States.

When does fc1adult.com expire?

fc1adult.com expires on 15 July 2027 according to https://rdap.verisign.com/com/v1/domain/fc1adult.com.

Who owns fc1adult.com?

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

Sources

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

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.