tdigirefah.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
30
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
30
tdigirefah.com was registered on 14 Nov 2018 via 1API GmbH and the registry expiry is 14 Nov 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/tdigirefah.com.
tdigirefah.com publishes 2 nameservers. DNSSEC is not signed.
tdigirefah.com has 1 IPv4 address (185.10.73.152). The geolocation database places 185.10.73.152 in Tehran (District 7), Iran.
No safety warning was recorded for tdigirefah.com in the checks that ran.
tdigirefah.com was registered on 14 Nov 2018 via 1API GmbH. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/tdigirefah.com.
| Registered | since 14 Nov 2018 |
|---|---|
| Created | 14 November 2018 |
| Updated | 4 October 2026 |
| Expires | 14 November 2027 |
| Registrar | 1API GmbH |
| Status | client transfer prohibited |
| Nameservers | ns1.newtdigirefah.com, ns2.newtdigirefah.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/tdigirefah.com |
tdigirefah.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.newtdigirefah.com is published for tdigirefah.com in the registration record from https://rdap.verisign.com/com/v1/domain/tdigirefah.com.
Nameserver ns2.newtdigirefah.com is published for tdigirefah.com in the registration record from https://rdap.verisign.com/com/v1/domain/tdigirefah.com.
tdigirefah.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.10.73.152 |
|---|---|
| AAAA | — |
| NS | ns1.tdigirefah.ir, ns2.tdigirefah.ir |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.10.73.152 answers for tdigirefah.com at resolver 1.1.1.1:53.
A random label under tdigirefah.com also resolved, which means wildcard DNS is on.
tdigirefah.com is placed in Tehran (District 7), Iran by the local geolocation database (db-ip).
| Address | 185.10.73.152 |
|---|---|
| Country | Iran |
| City | Tehran (District 7) |
| Source | db-ip |
No TLS certificate was read for tdigirefah.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
read tcp 10.0.0.3:48186->185.10.73.152:443: read: connection reset by peer
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://tdigirefah.com/": read tcp 10.0.0.3:48208->185.10.73.152:443: read: connection reset by peer
Family DNS for tdigirefah.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.
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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
tdigirefah.com is placed in Tehran (District 7), Iran.
tdigirefah.com expires on 14 November 2027 according to https://rdap.verisign.com/com/v1/domain/tdigirefah.com.
The registry did not return a person or a company for tdigirefah.com. RDAP often redacts the registrant. The registrar on file is 1API GmbH.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.