footybite.com

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

Online · 200SafeSSL: 67 days leftUnder 1 year old

One re-check per domain each UTC day.

67

footybite.com was registered on 21 Apr 2026 via Spaceship, Inc. and the registry expiry is 21 Apr 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/footybite.com.

footybite.com publishes 2 nameservers. DNSSEC is not signed.

footybite.com has 2 IPv4 addresses (13.248.169.48, 76.223.54.146). The geolocation database places 13.248.169.48 in Montreal, Canada.

The TLS certificate from GoDaddy TLS Intermediate CA DV - R1v1 is valid and has 67 days left (TLS 1.3). The homepage answered HTTP 200.

No safety warning was recorded for footybite.com in the checks that ran.

Domain · RDAP/WHOIS

footybite.com was registered on 21 Apr 2026 via Spaceship, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/footybite.com.

Registeredsince 21 Apr 2026
Created21 April 2026
Updated29 June 2026
Expires21 April 2028
RegistrarSpaceship, Inc.
Statusclient transfer prohibited
Nameserversns3.afternic.com, ns4.afternic.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/footybite.com

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

Nameserver ns4.afternic.com is published for footybite.com in the registration record from https://rdap.verisign.com/com/v1/domain/footybite.com.

DNS

footybite.com has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A13.248.169.48, 76.223.54.146
AAAA—
NSns3.afternic.com, ns4.afternic.com
MX (0)
SPFpresent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at footybite.com is "v=spf1 -all".

IPv4 address 13.248.169.48 answers for footybite.com at resolver 1.1.1.1:53.

IPv4 address 76.223.54.146 answers for footybite.com at resolver 1.1.1.1:53.

Mail exchanger has preference 0.

A random label under footybite.com also resolved, which means wildcard DNS is on.

Hosting and geo

footybite.com is placed in Montreal, Canada by the local geolocation database (db-ip).

Address13.248.169.48
CountryCanada
CityMontreal
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for footybite.com is valid, with 67 days left and 1 subject alternative name. Source: tls:443.

IssuerGoDaddy TLS Intermediate CA DV - R1v1
Subjectfootybite.com
Valid from23 June 2026
Valid until7 January 2027
Days left67
SAN count1
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: footybite.com.

Tech stack

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

The fingerprint set matched no product. That is a result, not a skipped check.

On-page checks

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

Status200
TTFB126 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links0
Images0
Faviconno

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

Change history

  • October 2026: geo city changed from empty to Montreal.
  • October 2026: geo country changed from empty to Canada.

Questions

Is footybite.com 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.com?

footybite.com is placed in Montreal, Canada.

When does footybite.com expire?

footybite.com expires on 21 April 2028 according to https://rdap.verisign.com/com/v1/domain/footybite.com.

Who owns footybite.com?

The registry did not return a person or a company for footybite.com. RDAP often redacts the registrant. The registrar on file is Spaceship, Inc..

Sources

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

Methodology

Related reports

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

.com Spaceship, 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.