bregvisioncloud.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
bregvisioncloud.com was registered on 10 May 2019 via Amazon Registrar, Inc. and the registry expiry is 10 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bregvisioncloud.com.
bregvisioncloud.com publishes 2 nameservers. DNSSEC is not signed.
bregvisioncloud.com has 3 IPv4 addresses (104.26.2.207, 104.26.3.207, 172.67.72.145) and 3 IPv6 addresses (2606:4700:20::681a:2cf, 2606:4700:20::681a:3cf, 2606:4700:20::ac43:4891). The geolocation database places 104.26.2.207 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 64 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon Web Services, Cloudflare and HSTS. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for bregvisioncloud.com in the checks that ran.
bregvisioncloud.com was registered on 10 May 2019 via Amazon Registrar, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/bregvisioncloud.com.
| Registered | since 10 May 2019 |
|---|---|
| Created | 10 May 2019 |
| Updated | 5 April 2026 |
| Expires | 10 May 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | active |
| Nameservers | jason.ns.cloudflare.com, kay.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/bregvisioncloud.com |
Nameserver jason.ns.cloudflare.com is published for bregvisioncloud.com in the registration record from https://rdap.verisign.com/com/v1/domain/bregvisioncloud.com.
Nameserver kay.ns.cloudflare.com is published for bregvisioncloud.com in the registration record from https://rdap.verisign.com/com/v1/domain/bregvisioncloud.com.
bregvisioncloud.com has 6 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.2.207, 104.26.3.207, 172.67.72.145 |
|---|---|
| AAAA | 2606:4700:20::681a:2cf, 2606:4700:20::681a:3cf, 2606:4700:20::ac43:4891 |
| NS | jason.ns.cloudflare.com, kay.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.bregvisioncloud.com is "v=DMARC1;p=none;".
IPv4 address 104.26.2.207 answers for bregvisioncloud.com at resolver 1.1.1.1:53.
IPv4 address 104.26.3.207 answers for bregvisioncloud.com at resolver 1.1.1.1:53.
IPv4 address 172.67.72.145 answers for bregvisioncloud.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:2cf answers for bregvisioncloud.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:3cf answers for bregvisioncloud.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4891 answers for bregvisioncloud.com at resolver 1.1.1.1:53.
bregvisioncloud.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.2.207 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for bregvisioncloud.com is valid, with 64 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | bregvisioncloud.com |
| Valid from | 5 October 2026 |
| Valid until | 3 January 2027 |
| Days left | 64 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.bregvisioncloud.com, bregvisioncloud.com.
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
Cloudflare is filed under CDN.
HSTS is filed under Security.
The homepage returned HTTP 200 in 28 ms. The target title is 11 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 28 ms |
| Title length | 11 yes |
| Quoted title | "Breg Vision" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | DENY |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 0 |
| Images | 0 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for bregvisioncloud.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 | yes |
| 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.
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 10 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
bregvisioncloud.com is placed in Toronto, Canada.
bregvisioncloud.com expires on 10 May 2027 according to https://rdap.verisign.com/com/v1/domain/bregvisioncloud.com.
The registry did not return a person or a company for bregvisioncloud.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.