bdgosms.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 84 days leftUnder 1 year old
62
bdgosms.com was registered on 29 Jun 2026 via NameSilo, LLC and the registry expiry is 29 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bdgosms.com.
bdgosms.com publishes 2 nameservers. DNSSEC is not signed.
bdgosms.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 84 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HTTP/3, LiteSpeed, LiteSpeed Cache, Litespeed Cache and PHP. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for bdgosms.com in the checks that ran.
Domain · RDAP/WHOIS
bdgosms.com was registered on 29 Jun 2026 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/bdgosms.com.
| Registered | since 29 Jun 2026 |
|---|---|
| Created | 29 June 2026 |
| Updated | 29 June 2026 |
| Expires | 29 June 2027 |
| Registrar | NameSilo, LLC |
| Status | active |
| Nameservers | betty.ns.cloudflare.com, justin.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/bdgosms.com |
Nameserver betty.ns.cloudflare.com is published for bdgosms.com in the registration record from https://rdap.verisign.com/com/v1/domain/bdgosms.com.
Nameserver justin.ns.cloudflare.com is published for bdgosms.com in the registration record from https://rdap.verisign.com/com/v1/domain/bdgosms.com.
DNS
bdgosms.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | betty.ns.cloudflare.com, justin.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.4 answers for bdgosms.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for bdgosms.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for bdgosms.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for bdgosms.com at resolver 1.1.1.1:53.
Hosting and geo
bdgosms.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for bdgosms.com is valid, with 84 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | bdgosms.com |
| Valid from | 25 October 2026 |
| Valid until | 23 January 2027 |
| Days left | 84 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bdgosms.com, bdgosms.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- PHP · Programming languages
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
PHP is filed under Programming languages.
On-page checks
The homepage returned HTTP 200 in 532 ms. The target title is 10 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 532 ms |
| Title length | 10 yes |
| Quoted title | "Index of /" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 3 |
| 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 bdgosms.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 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
Questions
Is bdgosms.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 bdgosms.com?
bdgosms.com is placed in Toronto, Canada.
When does bdgosms.com expire?
bdgosms.com expires on 29 June 2027 according to https://rdap.verisign.com/com/v1/domain/bdgosms.com.
Who owns bdgosms.com?
The registry did not return a person or a company for bdgosms.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/bdgosms.com at 2026-10-30T13:46:26Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:46:26Z
- TLS source tls:443 at 2026-10-30T13:46:26Z
- HTTP source https://bdgosms.com/ at 2026-10-30T13:46:26Z
- Tech source wappalyzergo at 2026-10-30T13:46:26Z
- Geo source db-ip at 2026-10-30T13:46:26Z
- Safety source family DNS and local lists at 2026-10-30T13:46:26Z
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.