bunkr.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -2673 days left17 years old
35
bunkr.com was registered on 8 May 2009 via Alpine Domains Inc. and the registry expiry is 8 May 2029. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bunkr.com.
bunkr.com publishes 3 nameservers. DNSSEC is not signed.
bunkr.com has 2 IPv4 addresses (15.175.248.72, 52.60.146.189). The geolocation database places 15.175.248.72 in Montreal, Canada.
The TLS certificate from My Company Ltd is not valid (TLS 1.3).
No safety warning was recorded for bunkr.com in the checks that ran.
Domain · RDAP/WHOIS
bunkr.com was registered on 8 May 2009 via Alpine Domains Inc.. The registry returned 1 status value and 3 nameservers from https://rdap.verisign.com/com/v1/domain/bunkr.com.
| Registered | since 8 May 2009 |
|---|---|
| Created | 8 May 2009 |
| Updated | 22 October 2026 |
| Expires | 8 May 2029 |
| Registrar | Alpine Domains Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.power-dns.com, ns2.power-dns.com, ns3.power-dns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/bunkr.com |
bunkr.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 ns1.power-dns.com is published for bunkr.com in the registration record from https://rdap.verisign.com/com/v1/domain/bunkr.com.
Nameserver ns2.power-dns.com is published for bunkr.com in the registration record from https://rdap.verisign.com/com/v1/domain/bunkr.com.
Nameserver ns3.power-dns.com is published for bunkr.com in the registration record from https://rdap.verisign.com/com/v1/domain/bunkr.com.
DNS
bunkr.com has 2 address records, 2 mail exchangers and 3 nameservers, measured at 1.1.1.1:53.
| A | 15.175.248.72, 52.60.146.189 |
|---|---|
| AAAA | — |
| NS | ns1.power-dns.com, ns2.power-dns.com, ns3.power-dns.com |
| MX | mx1.ewebdevelopment.com (1), mx2.ewebdevelopment.com (5) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at bunkr.com is "v=spf1 include:u2069692.wl.sendgrid.net -all".
IPv4 address 15.175.248.72 answers for bunkr.com at resolver 1.1.1.1:53.
IPv4 address 52.60.146.189 answers for bunkr.com at resolver 1.1.1.1:53.
Mail exchanger mx1.ewebdevelopment.com has preference 1.
Mail exchanger mx2.ewebdevelopment.com has preference 5.
A random label under bunkr.com also resolved, which means wildcard DNS is on.
Hosting and geo
bunkr.com is placed in Montreal, Canada by the local geolocation database (db-ip).
| Address | 15.175.248.72 |
|---|---|
| Country | Canada |
| City | Montreal |
| Source | db-ip |
SSL/TLS
The certificate for bunkr.com is not valid, with -2673 days left and 0 subject alternative names. Source: tls:443.
| Issuer | My Company Ltd |
|---|---|
| Subject | — |
| Valid from | 9 July 2009 |
| Valid until | 7 July 2019 |
| Days left | -2673 |
| SAN count | 0 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://bunkr.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T13:48:07Z is after 2019-07-07T22:11:02Z
Security
Family DNS for bunkr.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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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 5 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 bunkr.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 bunkr.com?
bunkr.com is placed in Montreal, Canada.
When does bunkr.com expire?
bunkr.com expires on 8 May 2029 according to https://rdap.verisign.com/com/v1/domain/bunkr.com.
Who owns bunkr.com?
The registry did not return a person or a company for bunkr.com. RDAP often redacts the registrant. The registrar on file is Alpine Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/bunkr.com at 2026-10-30T13:48:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:48:07Z
- TLS source tls:443 at 2026-10-30T13:48:07Z
- HTTP source https://bunkr.com/ at 2026-10-30T13:48:07Z
- Tech source not available at 2026-10-30T13:48:07Z
- Geo source db-ip at 2026-10-30T13:48:07Z
- Safety source family DNS and local lists at 2026-10-30T13:48:07Z
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.