arivify.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 76 days left13 years old
55
arivify.com was registered on 3 Mar 2013 via TurnCommerce, Inc. DBA NameBright.com and the registry expiry is 3 Mar 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/arivify.com.
arivify.com publishes 2 nameservers. DNSSEC is not signed.
arivify.com has 2 IPv4 addresses (104.21.84.77, 172.67.188.167) and 2 IPv6 addresses (2606:4700:3034::ac43:bca7, 2606:4700:3035::6815:544d). The geolocation database places 104.21.84.77 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 76 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for arivify.com in the checks that ran.
Domain · RDAP/WHOIS
arivify.com was registered on 3 Mar 2013 via TurnCommerce, Inc. DBA NameBright.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/arivify.com.
| Registered | since 3 Mar 2013 |
|---|---|
| Created | 3 March 2013 |
| Updated | 19 August 2026 |
| Expires | 3 March 2028 |
| Registrar | TurnCommerce, Inc. DBA NameBright.com |
| Status | client transfer prohibited |
| Nameservers | deb.ns.cloudflare.com, george.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/arivify.com |
arivify.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 deb.ns.cloudflare.com is published for arivify.com in the registration record from https://rdap.verisign.com/com/v1/domain/arivify.com.
Nameserver george.ns.cloudflare.com is published for arivify.com in the registration record from https://rdap.verisign.com/com/v1/domain/arivify.com.
DNS
arivify.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.84.77, 172.67.188.167 |
|---|---|
| AAAA | 2606:4700:3034::ac43:bca7, 2606:4700:3035::6815:544d |
| NS | deb.ns.cloudflare.com, george.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.84.77 answers for arivify.com at resolver 1.1.1.1:53.
IPv4 address 172.67.188.167 answers for arivify.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:bca7 answers for arivify.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:544d answers for arivify.com at resolver 1.1.1.1:53.
Hosting and geo
arivify.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.84.77 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for arivify.com is valid, with 76 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | arivify.com |
| Valid from | 17 October 2026 |
| Valid until | 15 January 2027 |
| Days left | 76 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.arivify.com, arivify.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 16 ms. The target title is 32 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 16 ms |
| Title length | 32 yes |
| Quoted title | "Attention Required! | Cloudflare" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex, nofollow |
| Canonical | — |
| Language | en-US |
| Links | 1 |
| Images | 0 |
| Favicon | no |
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 arivify.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 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 5 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
First checked on 30 October 2026; changes will appear here.
Questions
Is arivify.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 arivify.com?
arivify.com is placed in Toronto, Canada.
When does arivify.com expire?
arivify.com expires on 3 March 2028 according to https://rdap.verisign.com/com/v1/domain/arivify.com.
Who owns arivify.com?
The registry did not return a person or a company for arivify.com. RDAP often redacts the registrant. The registrar on file is TurnCommerce, Inc. DBA NameBright.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/arivify.com at 2026-10-30T13:45:12Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:45:12Z
- TLS source tls:443 at 2026-10-30T13:45:12Z
- HTTP source https://arivify.com/ at 2026-10-30T13:45:12Z
- Tech source wappalyzergo at 2026-10-30T13:45:12Z
- Geo source db-ip at 2026-10-30T13:45:12Z
- Safety source family DNS and local lists at 2026-10-30T13:45:12Z
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.