footybite.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -31 days left5 years oldTranco #914578
30
footybite.to was registered on 30 Jul 2021 via Spaceship, Inc. and the registry expiry is 30 Jul 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/footybite.to.
footybite.to publishes 2 nameservers. DNSSEC is not signed.
footybite.to has 1 IPv4 address (54.235.210.28). The geolocation database places 54.235.210.28 in Ashburn, United States.
The TLS certificate from YE1 is not valid (TLS 1.3).
No safety warning was recorded for footybite.to in the checks that ran.
Domain · RDAP/WHOIS
footybite.to was registered on 30 Jul 2021 via Spaceship, Inc.. The registry returned 3 status values and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/footybite.to.
| Registered | since 30 Jul 2021 |
|---|---|
| Created | 30 July 2021 |
| Updated | 30 June 2026 |
| Expires | 30 July 2027 |
| Registrar | Spaceship, Inc. |
| Status | server transfer prohibited, server update prohibited, server delete prohibited |
| Nameservers | ns1.seizedservers.com, ns2.seizedservers.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/footybite.to |
footybite.to carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
footybite.to carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
footybite.to carries the status "server delete prohibited". The registry itself is refusing deletes. This lock is not one the registrar can clear alone.
Nameserver ns1.seizedservers.com is published for footybite.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/footybite.to.
Nameserver ns2.seizedservers.com is published for footybite.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/footybite.to.
DNS
footybite.to has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 54.235.210.28 |
|---|---|
| AAAA | — |
| NS | ns1.seizedservers.com, ns2.seizedservers.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 54.235.210.28 answers for footybite.to at resolver 1.1.1.1:53.
A random label under footybite.to also resolved, which means wildcard DNS is on.
Hosting and geo
footybite.to is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 54.235.210.28 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
The certificate for footybite.to is not valid, with -31 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | footybite.to |
| Valid from | 1 July 2026 |
| Valid until | 29 September 2026 |
| Days left | -31 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: footybite.to.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://footybite.to/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T15:15:59Z is after 2026-09-29T18:43:06Z
Security
Family DNS for footybite.to is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
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 0 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 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is footybite.to 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 footybite.to?
footybite.to is placed in Ashburn, United States.
When does footybite.to expire?
footybite.to expires on 30 July 2027 according to https://rdap.tonicregistry.to/rdap/domain/footybite.to.
Who owns footybite.to?
The registry did not return a person or a company for footybite.to. RDAP often redacts the registrant. The registrar on file is Spaceship, Inc..
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/footybite.to at 2026-10-30T15:15:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:15:59Z
- TLS source tls:443 at 2026-10-30T15:15:59Z
- HTTP source https://footybite.to/ at 2026-10-30T15:15:59Z
- Tech source not available at 2026-10-30T15:15:59Z
- Geo source db-ip at 2026-10-30T15:15:59Z
- Safety source family DNS and local lists at 2026-10-30T15:15:59Z
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.