bingoport.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 50 days left19 years oldTranco #513038
80
bingoport.com was registered on 26 Feb 2007 via Squarespace Domains II LLC and the registry expiry is 26 Feb 2031. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bingoport.com.
bingoport.com publishes 4 nameservers. DNSSEC is signed.
bingoport.com has 1 IPv4 address (165.245.156.173). The geolocation database places 165.245.156.173 in Kansas City (Downtown Kansas City), United States.
The TLS certificate from YE1 is valid and has 50 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Google AdSense, Google Analytics, Google Tag Manager, Nginx, PHP, Stimulus and reCAPTCHA. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for bingoport.com in the checks that ran.
Domain · RDAP/WHOIS
bingoport.com was registered on 26 Feb 2007 via Squarespace Domains II LLC. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/bingoport.com.
| Registered | since 26 Feb 2007 |
|---|---|
| Created | 26 February 2007 |
| Updated | 14 June 2024 |
| Expires | 26 February 2031 |
| Registrar | Squarespace Domains II LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/bingoport.com |
bingoport.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.
bingoport.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 ns-cloud-a1.googledomains.com is published for bingoport.com in the registration record from https://rdap.verisign.com/com/v1/domain/bingoport.com.
Nameserver ns-cloud-a2.googledomains.com is published for bingoport.com in the registration record from https://rdap.verisign.com/com/v1/domain/bingoport.com.
Nameserver ns-cloud-a3.googledomains.com is published for bingoport.com in the registration record from https://rdap.verisign.com/com/v1/domain/bingoport.com.
Nameserver ns-cloud-a4.googledomains.com is published for bingoport.com in the registration record from https://rdap.verisign.com/com/v1/domain/bingoport.com.
DNS
bingoport.com has 1 address record, 2 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 165.245.156.173 |
|---|---|
| AAAA | — |
| NS | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| MX | mx1.improvmx.com (10), mx2.improvmx.com (20) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at bingoport.com is "v=spf1 include:spf.improvmx.com ~all".
The DMARC text record at _dmarc.bingoport.com is "v=DMARC1; p=none;".
IPv4 address 165.245.156.173 answers for bingoport.com at resolver 1.1.1.1:53.
Mail exchanger mx1.improvmx.com has preference 10.
Mail exchanger mx2.improvmx.com has preference 20.
Hosting and geo
bingoport.com is placed in Kansas City (Downtown Kansas City), United States by the local geolocation database (db-ip).
| Address | 165.245.156.173 |
|---|---|
| Country | United States |
| City | Kansas City (Downtown Kansas City) |
| Source | db-ip |
SSL/TLS
The certificate for bingoport.com is valid, with 50 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | www.bingoport.com |
| Valid from | 22 September 2026 |
| Valid until | 21 December 2026 |
| Days left | 50 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: bingoport.com, www.bingoport.com.
Tech stack
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
- Google AdSense · Advertising
- Google Analytics · Analytics
- Google Tag Manager · Tag managers
- Nginx · Web servers, Reverse proxies
- PHP · Programming languages
- Stimulus · JavaScript frameworks
- reCAPTCHA · Security
Google AdSense is filed under Advertising.
Google Analytics is filed under Analytics.
Google Tag Manager is filed under Tag managers.
Nginx is filed under Web servers, Reverse proxies.
PHP is filed under Programming languages.
Stimulus is filed under JavaScript frameworks.
reCAPTCHA is filed under Security.
On-page checks
The homepage returned HTTP 200 in 141 ms. The target title is 45 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 141 ms |
| Title length | 45 yes |
| Quoted title | "Bingoport.com Free Bingo with Genuine Rewards" |
| Meta description | "Welcome to Bingoport.com - America's only Free Bingo site with genuine prizes and rewards" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://www.bingoport.com |
| Language | en-GB |
| Links | 27 |
| Images | 10 |
| Favicon | yes |
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 bingoport.com 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 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 15 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 Kansas City (Downtown Kansas City).
- October 2026: geo country changed from empty to United States.
Questions
Is bingoport.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 bingoport.com?
bingoport.com is placed in Kansas City (Downtown Kansas City), United States.
When does bingoport.com expire?
bingoport.com expires on 26 February 2031 according to https://rdap.verisign.com/com/v1/domain/bingoport.com.
Who owns bingoport.com?
The registry did not return a person or a company for bingoport.com. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/bingoport.com at 2026-10-30T13:47:06Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:06Z
- TLS source tls:443 at 2026-10-30T13:47:06Z
- HTTP source https://bingoport.com/ at 2026-10-30T13:47:06Z
- Tech source wappalyzergo at 2026-10-30T13:47:06Z
- Geo source db-ip at 2026-10-30T13:47:06Z
- Safety source family DNS and local lists at 2026-10-30T13:47:06Z
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.