feed2all.org

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

Online · 200SafeSSL: 55 days left13 years old

One re-check per domain each UTC day.

70

feed2all.org was registered on 16 Aug 2013 via Gransy, s.r.o. and the registry expiry is 16 Aug 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/feed2all.org.

feed2all.org publishes 1 nameserver. DNSSEC is not signed.

feed2all.org has 1 IPv4 address (91.224.59.102). The geolocation database places 91.224.59.102 in Prague, Czechia.

The TLS certificate from YE2 is valid and has 55 days left (TLS 1.2). The homepage answered HTTP 200.

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

No safety warning was recorded for feed2all.org in the checks that ran.

Domain · RDAP/WHOIS

feed2all.org was registered on 16 Aug 2013 via Gransy, s.r.o.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/feed2all.org.

Registeredsince 16 Aug 2013
Created16 August 2013
Updated12 August 2026
Expires16 August 2027
RegistrarGransy, s.r.o.
Statusactive
Nameservers26.dkimsoa.xyz, j.dkimsoa.xyz
DNSSECno
Sourcehttps://rdap.publicinterestregistry.org/rdap/domain/feed2all.org

Nameserver 26.dkimsoa.xyz is published for feed2all.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/feed2all.org.

Nameserver j.dkimsoa.xyz is published for feed2all.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/feed2all.org.

DNS

feed2all.org has 1 address record, 1 mail exchanger and 1 nameserver, measured at 1.1.1.1:53.

A91.224.59.102
AAAA—
NS—
MXaspmx.l.google.com (10) Google
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 91.224.59.102 answers for feed2all.org at resolver 1.1.1.1:53.

Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.

Hosting and geo

feed2all.org is placed in Prague, Czechia by the local geolocation database (db-ip).

Address91.224.59.102
CountryCzechia
CityPrague
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for feed2all.org is valid, with 55 days left and 2 subject alternative names. Source: tls:443.

IssuerYE2
Subjectfeed2all.org
Valid from26 September 2026
Valid until25 December 2026
Days left55
SAN count2
ProtocolTLS 1.2
Sourcetls:443

Subject alternative names: feed2all.org, www.feed2all.org.

Tech stack

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

  • Google Analytics · Analytics
  • Google Hosted Libraries · CDN
  • Nginx · Web servers, Reverse proxies
  • jQuery · JavaScript libraries

Google Analytics is filed under Analytics.

Google Hosted Libraries is filed under CDN.

Nginx is filed under Web servers, Reverse proxies.

jQuery is filed under JavaScript libraries.

On-page checks

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

Status200
TTFB57 ms
Title length47 yes
Quoted title"Feed2All - Soccer Streams - Football Broadcasts"
Meta description"Feed2All the best channel on the market with free streams for everyone. Watch football and soccer for free in the highest quality with TheFeed2All and Firstrow streams." yes
H1 count0
HSTSno no
CSPno
X-Frame-OptionsDENY
Robots meta—
Canonicalhttps://feed2all.org
Languageen
Links38
Images8
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 feed2all.org 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 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 Prague.
  • October 2026: geo country changed from empty to Czechia.

Questions

Is feed2all.org 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 feed2all.org?

feed2all.org is placed in Prague, Czechia.

When does feed2all.org expire?

feed2all.org expires on 16 August 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/feed2all.org.

Who owns feed2all.org?

The registry did not return a person or a company for feed2all.org. RDAP often redacts the registrant. The registrar on file is Gransy, s.r.o..

Sources

  • RDAP source https://rdap.publicinterestregistry.org/rdap/domain/feed2all.org at 2026-10-30T15:02:11Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:02:11Z
  • TLS source tls:443 at 2026-10-30T15:02:11Z
  • HTTP source https://feed2all.org/ at 2026-10-30T15:02:11Z
  • Tech source wappalyzergo at 2026-10-30T15:02:11Z
  • Geo source db-ip at 2026-10-30T15:02:11Z
  • Safety source family DNS and local lists at 2026-10-30T15:02:11Z

Methodology

Related reports

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

.org Gransy, s.r.o.

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.