evojav.pro

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

HTTP 403Family DNS blockedSSL: 79 days left5 years oldTranco #80305

One re-check per domain each UTC day.

45

evojav.pro was registered on 31 Dec 2020 via NameSilo, LLC and the registry expiry is 31 Dec 2026. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/evojav.pro.

evojav.pro publishes 2 nameservers. DNSSEC is not signed.

evojav.pro has 3 IPv4 addresses (104.26.0.99, 104.26.1.99, 172.67.74.42). The geolocation database places 104.26.0.99 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 79 days left (TLS 1.3).

Tech detection named Cloudflare. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

evojav.pro was registered on 31 Dec 2020 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/evojav.pro.

Registeredsince 31 Dec 2020
Created31 December 2020
Updated12 August 2026
Expires31 December 2026
RegistrarNameSilo, LLC
Statusclient transfer prohibited
Nameserversnaya.ns.cloudflare.com, carmelo.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.identitydigital.services/rdap/domain/evojav.pro

evojav.pro 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 naya.ns.cloudflare.com is published for evojav.pro in the registration record from https://rdap.identitydigital.services/rdap/domain/evojav.pro.

Nameserver carmelo.ns.cloudflare.com is published for evojav.pro in the registration record from https://rdap.identitydigital.services/rdap/domain/evojav.pro.

DNS

evojav.pro has 3 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.26.0.99, 104.26.1.99, 172.67.74.42
AAAA—
NScarmelo.ns.cloudflare.com, naya.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.26.0.99 answers for evojav.pro at resolver 1.1.1.1:53.

IPv4 address 104.26.1.99 answers for evojav.pro at resolver 1.1.1.1:53.

IPv4 address 172.67.74.42 answers for evojav.pro at resolver 1.1.1.1:53.

Hosting and geo

evojav.pro is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.26.0.99
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for evojav.pro is valid, with 79 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectevojav.pro
Valid from20 October 2026
Valid until18 January 2027
Days left79
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.evojav.pro, evojav.pro.

Tech stack

Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.

  • Cloudflare · CDN

Cloudflare is filed under CDN.

On-page checks

The homepage returned HTTP 403 in 30 ms. The target title is 16 characters and the page has 0 H1 headings.

Status403
TTFB30 ms
Title length16 yes
Quoted title"Just a moment..."
Meta descriptionnone no
H1 count0
HSTSno no
CSPyes
X-Frame-OptionsSAMEORIGIN
Robots metanoindex,nofollow
Canonical—
Languageen-US
Links0
Images0
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for evojav.pro is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPyes

Cloudflare family DNS returned a block for evojav.pro. That resolver covers adult and malware names.

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 20 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 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 0 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

First checked on 30 October 2026; changes will appear here.

Questions

Is evojav.pro safe?

Cloudflare family DNS returned a block for evojav.pro. That resolver covers adult and malware names.

Who hosts evojav.pro?

evojav.pro is placed in Toronto, Canada.

When does evojav.pro expire?

evojav.pro expires on 31 December 2026 according to https://rdap.identitydigital.services/rdap/domain/evojav.pro.

Who owns evojav.pro?

The registry did not return a person or a company for evojav.pro. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.

Sources

  • RDAP source https://rdap.identitydigital.services/rdap/domain/evojav.pro at 2026-10-30T15:56:28Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:56:28Z
  • TLS source tls:443 at 2026-10-30T15:56:28Z
  • HTTP source https://evojav.pro/ at 2026-10-30T15:56:28Z
  • Tech source wappalyzergo at 2026-10-30T15:56:28Z
  • Geo source db-ip at 2026-10-30T15:56:28Z
  • Safety source family DNS and local lists at 2026-10-30T15:56:28Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.pro NameSilo, LLC

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.

Removal policy

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.