flingster.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 39 days left24 years oldTranco #39827
65
flingster.com was registered on 5 Jun 2002 via GoDaddy.com, LLC and the registry expiry is 5 Jun 2034. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/flingster.com.
flingster.com publishes 2 nameservers. DNSSEC is signed.
flingster.com has 2 IPv4 addresses (104.18.39.170, 172.64.148.86). The geolocation database places 104.18.39.170 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 39 days left (TLS 1.3).
Tech detection named Cloudflare, Cloudflare Bot Management, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
flingster.com was registered on 5 Jun 2002 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/flingster.com.
| Registered | since 5 Jun 2002 |
|---|---|
| Created | 5 June 2002 |
| Updated | 19 March 2025 |
| Expires | 5 June 2034 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | chip.ns.cloudflare.com, wanda.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/flingster.com |
flingster.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
flingster.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
flingster.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.
flingster.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver chip.ns.cloudflare.com is published for flingster.com in the registration record from https://rdap.verisign.com/com/v1/domain/flingster.com.
Nameserver wanda.ns.cloudflare.com is published for flingster.com in the registration record from https://rdap.verisign.com/com/v1/domain/flingster.com.
DNS
flingster.com has 2 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.18.39.170, 172.64.148.86 |
|---|---|
| AAAA | — |
| NS | chip.ns.cloudflare.com, wanda.ns.cloudflare.com |
| MX | mail.protonmail.ch (10) Proton, mailsec.protonmail.ch (20) Proton |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at flingster.com is "v=spf1 include:_spf.protonmail.ch include:u3244063.wl064.sendgrid.net ~all".
The DMARC text record at _dmarc.flingster.com is "v=DMARC1; p=quarantine".
IPv4 address 104.18.39.170 answers for flingster.com at resolver 1.1.1.1:53.
IPv4 address 172.64.148.86 answers for flingster.com at resolver 1.1.1.1:53.
Mail exchanger mail.protonmail.ch has preference 10. The host is recognised as Proton.
Mail exchanger mailsec.protonmail.ch has preference 20. The host is recognised as Proton.
Hosting and geo
flingster.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.18.39.170 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for flingster.com is valid, with 39 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | flingster.com |
| Valid from | 11 September 2026 |
| Valid until | 10 December 2026 |
| Days left | 39 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.flingster.com, flingster.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- HSTS · Security
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 8 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 8 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 flingster.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | yes |
Cloudflare family DNS returned a block for flingster.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 10 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 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 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
First checked on 30 October 2026; changes will appear here.
Questions
Is flingster.com safe?
Cloudflare family DNS returned a block for flingster.com. That resolver covers adult and malware names.
Who hosts flingster.com?
flingster.com is placed in Toronto, Canada.
When does flingster.com expire?
flingster.com expires on 5 June 2034 according to https://rdap.verisign.com/com/v1/domain/flingster.com.
Who owns flingster.com?
The registry did not return a person or a company for flingster.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/flingster.com at 2026-10-30T13:54:44Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:54:44Z
- TLS source tls:443 at 2026-10-30T13:54:44Z
- HTTP source https://flingster.com/ at 2026-10-30T13:54:44Z
- Tech source wappalyzergo at 2026-10-30T13:54:44Z
- Geo source db-ip at 2026-10-30T13:54:44Z
- Safety source family DNS and local lists at 2026-10-30T13:54:44Z
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.