fulibus.net

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

Online · 200SafeSSL: 79 days left9 years old

One re-check per domain each UTC day.

70

fulibus.net was registered on 29 Nov 2016 via Automattic Inc. and the registry expiry is 29 Nov 2028. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/fulibus.net.

fulibus.net publishes 2 nameservers. DNSSEC is not signed.

fulibus.net has 1 IPv4 address (50.118.186.140). The geolocation database places 50.118.186.140 in Los Angeles, United States.

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

Tech detection named HSTS, HTTP/3, Nginx and jQuery. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for fulibus.net in the checks that ran.

Domain · RDAP/WHOIS

fulibus.net was registered on 29 Nov 2016 via Automattic Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/fulibus.net.

Registeredsince 29 Nov 2016
Created29 November 2016
Updated24 November 2025
Expires29 November 2028
RegistrarAutomattic Inc.
Statusclient transfer prohibited
Nameserversamir.ns.cloudflare.com, cruz.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/net/v1/domain/fulibus.net

fulibus.net 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 amir.ns.cloudflare.com is published for fulibus.net in the registration record from https://rdap.verisign.com/net/v1/domain/fulibus.net.

Nameserver cruz.ns.cloudflare.com is published for fulibus.net in the registration record from https://rdap.verisign.com/net/v1/domain/fulibus.net.

DNS

fulibus.net has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A50.118.186.140
AAAA—
NSamir.ns.cloudflare.com, cruz.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 50.118.186.140 answers for fulibus.net at resolver 1.1.1.1:53.

Hosting and geo

fulibus.net is placed in Los Angeles, United States by the local geolocation database (db-ip).

Address50.118.186.140
CountryUnited States
CityLos Angeles
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for fulibus.net is valid, with 79 days left and 2 subject alternative names. Source: tls:443.

IssuerYR2
Subjectwww.fulibus.net
Valid from20 October 2026
Valid until18 January 2027
Days left79
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: fulibus.net, www.fulibus.net.

Tech stack

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

  • HSTS · Security
  • HTTP/3 · Miscellaneous
  • Nginx · Web servers, Reverse proxies
  • jQuery · JavaScript libraries

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

Nginx is filed under Web servers, Reverse proxies.

jQuery is filed under JavaScript libraries.

On-page checks

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

Status200
TTFB247 ms
Title length11 yes
Quoted title"福利吧-分享你的福利吧"
Meta description"福利吧(fuliba2023)分享你的福利吧,每日更新福利汇总、电影推荐、购物网赚、美图摄影等精彩内容,发现更多有趣实用的网络福利。" yes
H1 count0
HSTSyes yes
CSPno
X-Frame-Options—
Robots metamax-image-preview:large
Canonicalhttps://fuliba2023.net/
Languagezh-CN
Links309
Images65
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 fulibus.net is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
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 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 5 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 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: geo city changed from empty to Los Angeles.
  • October 2026: geo country changed from empty to United States.

Questions

Is fulibus.net 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 fulibus.net?

fulibus.net is placed in Los Angeles, United States.

When does fulibus.net expire?

fulibus.net expires on 29 November 2028 according to https://rdap.verisign.com/net/v1/domain/fulibus.net.

Who owns fulibus.net?

The registry did not return a person or a company for fulibus.net. RDAP often redacts the registrant. The registrar on file is Automattic Inc..

Sources

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

Methodology

Related reports

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

.net Automattic 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.