defencify.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 67 days left9 years oldTranco #686809
75
defencify.org was registered on 21 Sep 2017 via GoDaddy.com, LLC and the registry expiry is 21 Sep 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/defencify.org.
defencify.org publishes 2 nameservers. DNSSEC is not signed.
defencify.org has 1 IPv4 address (52.139.5.147). The geolocation database places 52.139.5.147 in Toronto, Canada.
The TLS certificate from YR2 is valid and has 67 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named IIS, Microsoft ASP.NET, Prototype, Windows Server, jQuery and jQuery UI. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for defencify.org in the checks that ran.
Domain · RDAP/WHOIS
defencify.org was registered on 21 Sep 2017 via GoDaddy.com, LLC. The registry returned 5 status values and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/defencify.org.
| Registered | since 21 Sep 2017 |
|---|---|
| Created | 21 September 2017 |
| Updated | 22 September 2026 |
| Expires | 21 September 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited, auto renew period |
| Nameservers | ns13.domaincontrol.com, ns14.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/defencify.org |
defencify.org carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
defencify.org carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
defencify.org 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.
defencify.org carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns13.domaincontrol.com is published for defencify.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/defencify.org.
Nameserver ns14.domaincontrol.com is published for defencify.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/defencify.org.
DNS
defencify.org has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 52.139.5.147 |
|---|---|
| AAAA | — |
| NS | ns13.domaincontrol.com, ns14.domaincontrol.com |
| MX | defencify-org.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at defencify.org is "v=spf1 include:spf.protection.outlook.com -all".
IPv4 address 52.139.5.147 answers for defencify.org at resolver 1.1.1.1:53.
Mail exchanger defencify-org.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
defencify.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 52.139.5.147 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for defencify.org is valid, with 67 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | defencify.org |
| Valid from | 9 October 2026 |
| Valid until | 7 January 2027 |
| Days left | 67 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: defencify.org.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- IIS · Web servers
- Microsoft ASP.NET · Web frameworks
- Prototype · JavaScript frameworks
- Windows Server · Operating systems
- jQuery · JavaScript libraries
- jQuery UI · JavaScript libraries
IIS is filed under Web servers.
Microsoft ASP.NET is filed under Web frameworks.
Prototype is filed under JavaScript frameworks.
Windows Server is filed under Operating systems.
jQuery is filed under JavaScript libraries.
jQuery UI is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 99 ms. The target title is 36 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 99 ms |
| Title length | 36 yes |
| Quoted title | "Defencify Training Platform - Log In" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 4 |
| Images | 1 |
| Favicon | yes |
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 defencify.org 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 25 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 10 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 Toronto.
- October 2026: geo country changed from empty to Canada.
Questions
Is defencify.org 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 defencify.org?
defencify.org is placed in Toronto, Canada.
When does defencify.org expire?
defencify.org expires on 21 September 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/defencify.org.
Who owns defencify.org?
The registry did not return a person or a company for defencify.org. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/defencify.org at 2026-10-30T15:01:53Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:01:53Z
- TLS source tls:443 at 2026-10-30T15:01:53Z
- HTTP source https://defencify.org/ at 2026-10-30T15:01:53Z
- Tech source wappalyzergo at 2026-10-30T15:01:53Z
- Geo source db-ip at 2026-10-30T15:01:53Z
- Safety source family DNS and local lists at 2026-10-30T15:01:53Z
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.