kpdm.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe10 years old
30
kpdm.net was registered on 19 Jan 2016 via NameSilo, LLC and the registry expiry is 19 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/kpdm.net.
kpdm.net publishes 2 nameservers. DNSSEC is not signed.
kpdm.net has 1 IPv4 address (154.64.225.219). The geolocation database places 154.64.225.219 in Los Angeles (Central-Alameda), United States.
No safety warning was recorded for kpdm.net in the checks that ran.
Domain · RDAP/WHOIS
kpdm.net was registered on 19 Jan 2016 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/kpdm.net.
| Registered | since 19 Jan 2016 |
|---|---|
| Created | 19 January 2016 |
| Updated | 19 January 2026 |
| Expires | 19 January 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | sturgeon.dnspod.net, zinc.dnspod.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/kpdm.net |
kpdm.net 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 sturgeon.dnspod.net is published for kpdm.net in the registration record from https://rdap.verisign.com/net/v1/domain/kpdm.net.
Nameserver zinc.dnspod.net is published for kpdm.net in the registration record from https://rdap.verisign.com/net/v1/domain/kpdm.net.
DNS
kpdm.net has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 154.64.225.219 |
|---|---|
| AAAA | — |
| NS | sturgeon.dnspod.net, zinc.dnspod.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 154.64.225.219 answers for kpdm.net at resolver 1.1.1.1:53.
Hosting and geo
kpdm.net is placed in Los Angeles (Central-Alameda), United States by the local geolocation database (db-ip).
| Address | 154.64.225.219 |
|---|---|
| Country | United States |
| City | Los Angeles (Central-Alameda) |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for kpdm.net on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 154.64.225.219:443: i/o timeout
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 |
|---|
context deadline exceeded
Security
Family DNS for kpdm.net 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 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 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: tls issuer changed from LiteSSL RSA CA 2025 to empty.
- October 2026: tls not_after changed from 2027-01-07T15:59:59Z to empty.
- October 2026: tls protocol changed from TLS 1.3 to empty.
- October 2026: tls valid changed from true to false.
- October 2026: http status_class changed from 4xx to empty.
- October 2026: tech removed Nginx.
- October 2026: geo city changed from empty to Los Angeles (Central-Alameda).
- October 2026: geo country changed from empty to United States.
Questions
Is kpdm.net 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 kpdm.net?
kpdm.net is placed in Los Angeles (Central-Alameda), United States.
When does kpdm.net expire?
kpdm.net expires on 19 January 2027 according to https://rdap.verisign.com/net/v1/domain/kpdm.net.
Who owns kpdm.net?
The registry did not return a person or a company for kpdm.net. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/kpdm.net at 2026-10-30T14:53:04Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:53:04Z
- TLS source tls:443 at 2026-10-30T14:53:04Z
- HTTP source https://kpdm.net/ at 2026-10-30T14:53:04Z
- Tech source not available at 2026-10-30T14:53:04Z
- Geo source db-ip at 2026-10-30T14:53:04Z
- Safety source family DNS and local lists at 2026-10-30T14:53:04Z
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.