Report ID: #F9D8ADCA

ddb.im

Norway No HTTPS Updated
40
Moderate
AlphaFortify · ddb.im — Report card
AlphaFortify · ddb.im

ddb.im — independent inspection

Below: every public infrastructure fact our scanner could find on ddb.im, mapped onto an objective 0-100 score.

What we observed

Looking at ddb.im from the outside, the most important data points are its hosting country (Norway), the SSL state (No) and the registration footprint (Unknown).

Time on the open web

ddb.im has been visible to public DNS for roughly ? years. That is enough history to leave a reputation footprint, which we factor into the score.

Encryption (HTTPS)

HTTPS check returned No. A valid TLS certificate is the bare minimum any modern site should ship — its absence is a serious red flag.

Hosting & infrastructure

The domain currently resolves to a server in Norway, served by Unknown. Hosting location does not equal trust, but it tells you which jurisdiction handles the data.

Comparable domains

Sites with similar metadata to ddb.im — ? yrs, Norway hosting, valid SSL — typically include both legitimate businesses and rebranded shells. Treat the score as one signal among several.

Conclusion

After fusing DNS, TLS, RDAP and GeoIP signals, our automated score for ddb.im sits at 40/100 (moderate). Use it as a guideline, not a guarantee.

Technical Information

IP Address
195.204.78.83
Server Location
Norway
ISP / Provider
Unknown

SSL Certificate

SSL Certificate
No HTTPS

Registrar

Registrar
Unknown

What looks good

  • Uses modern HTTPS endpoints
  • Hosting on an established ISP network
  • Consistent A and AAAA records
  • Subject Alternative Names cover the domain correctly

What to watch

  • Reputation data is limited to public sources
  • Uses generic shared hosting (cannot identify operator from IP)
  • TXT records expose minimal trust hints

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →

Frequently Asked Questions

Is the WHOIS information about ddb.im hidden?
Most modern registrars apply privacy protection by default, so personal contact data may be redacted. Registration dates and registrar are still visible.
Is ddb.im on a security blocklist?
At the time of audit, ddb.im was not present in the public blocklists we sample (PhishTank, abuse feeds, etc.).
Is ddb.im a phishing website?
Our scanner does not perform visual similarity checks. We can only confirm that no obvious infrastructure markers (cert mismatch, fresh registration with high traffic) were triggered.
What looks risky about ddb.im?
For ddb.im we look at: age ? yrs, SSL No, registrar Unknown and hosting in Norway. Any single weak point can drag the technical confidence down.
How often is ddb.im re-checked?
By default the report is refreshed every 30 days, plus on every manual re-check from the dashboard.

This report is generated automatically from public technical signals. It is not legal or financial advice.