bitmitigate.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe9 years old
40
bitmitigate.com was registered on 3 Mar 2017 via Epik LLC and the registry expiry is 3 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bitmitigate.com.
bitmitigate.com publishes 2 nameservers. DNSSEC is not signed.
bitmitigate.com has 1 IPv4 address (45.88.202.101). The geolocation database places 45.88.202.101 in Sandefjord, Norway.
No safety warning was recorded for bitmitigate.com in the checks that ran.
Domain · RDAP/WHOIS
bitmitigate.com was registered on 3 Mar 2017 via Epik LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/bitmitigate.com.
| Registered | since 3 Mar 2017 |
|---|---|
| Created | 3 March 2017 |
| Updated | 18 February 2026 |
| Expires | 3 March 2027 |
| Registrar | Epik LLC |
| Status | client transfer prohibited |
| Nameservers | ns3.epik.com, ns4.epik.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/bitmitigate.com |
bitmitigate.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 ns3.epik.com is published for bitmitigate.com in the registration record from https://rdap.verisign.com/com/v1/domain/bitmitigate.com.
Nameserver ns4.epik.com is published for bitmitigate.com in the registration record from https://rdap.verisign.com/com/v1/domain/bitmitigate.com.
DNS
bitmitigate.com has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 45.88.202.101 |
|---|---|
| AAAA | — |
| NS | ns3.epik.com, ns4.epik.com |
| MX | mxb.mailgun.org (10), redir.epik.com (10), mxa.mailgun.org (20) |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org, issue trust-provider.com |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at bitmitigate.com is "v=spf1 a mx mx:mail.bitmitigate.com include:spf-a.jangomail.com include:spf-b.jangomail.com include:spf-c.jangomail.com include: mail.zendesk.com include:spf-d.jangomail.com ~all".
IPv4 address 45.88.202.101 answers for bitmitigate.com at resolver 1.1.1.1:53.
Mail exchanger mxb.mailgun.org has preference 10.
Mail exchanger redir.epik.com has preference 10.
Mail exchanger mxa.mailgun.org has preference 20.
A random label under bitmitigate.com also resolved, which means wildcard DNS is on.
Hosting and geo
bitmitigate.com is placed in Sandefjord, Norway by the local geolocation database (db-ip).
| Address | 45.88.202.101 |
|---|---|
| Country | Norway |
| City | Sandefjord |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for bitmitigate.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 45.88.202.101:443: connect: no route to host
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://bitmitigate.com/": dial tcp 45.88.202.101:443: connect: no route to host
Security
Family DNS for bitmitigate.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 10 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 Sandefjord.
- October 2026: geo country changed from empty to Norway.
Questions
Is bitmitigate.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 bitmitigate.com?
bitmitigate.com is placed in Sandefjord, Norway.
When does bitmitigate.com expire?
bitmitigate.com expires on 3 March 2027 according to https://rdap.verisign.com/com/v1/domain/bitmitigate.com.
Who owns bitmitigate.com?
The registry did not return a person or a company for bitmitigate.com. RDAP often redacts the registrant. The registrar on file is Epik LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/bitmitigate.com at 2026-10-30T13:47:17Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:17Z
- TLS source tls:443 at 2026-10-30T13:47:17Z
- HTTP source https://bitmitigate.com/ at 2026-10-30T13:47:17Z
- Tech source not available at 2026-10-30T13:47:17Z
- Geo source db-ip at 2026-10-30T13:47:17Z
- Safety source family DNS and local lists at 2026-10-30T13:47:17Z
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.