photometricviewer.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 58 days left21 years old
30
photometricviewer.com was registered on 1 Mar 2005 via Regional Network Information Center, JSC dba RU-CENTER and the registry expiry is 1 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/photometricviewer.com.
photometricviewer.com publishes 2 nameservers. DNSSEC is not signed.
photometricviewer.com has 1 IPv4 address (185.176.43.54). The geolocation database places 185.176.43.54 in Sofia, Bulgaria.
The TLS certificate from YR1 is not valid (TLS 1.2).
No safety warning was recorded for photometricviewer.com in the checks that ran.
Domain · RDAP/WHOIS
photometricviewer.com was registered on 1 Mar 2005 via Regional Network Information Center, JSC dba RU-CENTER. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/photometricviewer.com.
| Registered | since 1 Mar 2005 |
|---|---|
| Created | 1 March 2005 |
| Updated | 1 March 2026 |
| Expires | 1 March 2027 |
| Registrar | Regional Network Information Center, JSC dba RU-CENTER |
| Status | client transfer prohibited |
| Nameservers | ns1.atspace.me, ns2.atspace.me |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/photometricviewer.com |
photometricviewer.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.atspace.me is published for photometricviewer.com in the registration record from https://rdap.verisign.com/com/v1/domain/photometricviewer.com.
Nameserver ns2.atspace.me is published for photometricviewer.com in the registration record from https://rdap.verisign.com/com/v1/domain/photometricviewer.com.
DNS
photometricviewer.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.176.43.54 |
|---|---|
| AAAA | — |
| NS | ns1.atspace.me, ns2.atspace.me |
| MX | mx.photometricviewer.com (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.176.43.54 answers for photometricviewer.com at resolver 1.1.1.1:53.
Mail exchanger mx.photometricviewer.com has preference 10.
Hosting and geo
photometricviewer.com is placed in Sofia, Bulgaria by the local geolocation database (db-ip).
| Address | 185.176.43.54 |
|---|---|
| Country | Bulgaria |
| City | Sofia |
| Source | db-ip |
SSL/TLS
The certificate for photometricviewer.com is not valid, with 58 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | f5-preview.runhosting.com |
| Valid from | 30 September 2026 |
| Valid until | 29 December 2026 |
| Days left | 58 |
| SAN count | 1 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: f5-preview.runhosting.com.
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://photometricviewer.com/": tls: failed to verify certificate: x509: certificate is valid for f5-preview.runhosting.com, not photometricviewer.com
Security
Family DNS for photometricviewer.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 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: geo city changed from empty to Sofia.
- October 2026: geo country changed from empty to Bulgaria.
Questions
Is photometricviewer.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 photometricviewer.com?
photometricviewer.com is placed in Sofia, Bulgaria.
When does photometricviewer.com expire?
photometricviewer.com expires on 1 March 2027 according to https://rdap.verisign.com/com/v1/domain/photometricviewer.com.
Who owns photometricviewer.com?
The registry did not return a person or a company for photometricviewer.com. RDAP often redacts the registrant. The registrar on file is Regional Network Information Center, JSC dba RU-CENTER.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/photometricviewer.com at 2026-10-30T14:09:09Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:09:09Z
- TLS source tls:443 at 2026-10-30T14:09:09Z
- HTTP source https://photometricviewer.com/ at 2026-10-30T14:09:09Z
- Tech source not available at 2026-10-30T14:09:09Z
- Geo source db-ip at 2026-10-30T14:09:09Z
- Safety source family DNS and local lists at 2026-10-30T14:09:09Z
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.