pj.ca
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
pj.ca was registered on 17 Oct 2000 via Webnames.ca Inc. and the registry expiry is 1 Sep 2029. WHOIS data came from RDAP at https://rdap.ca.fury.ca/rdap/domain/pj.ca.
pj.ca publishes 4 nameservers. DNSSEC is not signed.
pj.ca has 4 IPv4 addresses (65.8.131.129, 65.8.131.26, 65.8.131.36, 65.8.131.42). The geolocation database places 65.8.131.129 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 94 days left (TLS 1.3).
Tech detection named Amazon CloudFront and Amazon Web Services. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for pj.ca in the checks that ran.
pj.ca was registered on 17 Oct 2000 via Webnames.ca Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.ca.fury.ca/rdap/domain/pj.ca.
| Registered | since 17 Oct 2000 |
|---|---|
| Created | 17 October 2000 |
| Updated | 14 October 2026 |
| Expires | 1 September 2029 |
| Registrar | Webnames.ca Inc. |
| Status | client transfer prohibited |
| Nameservers | ns-1334.awsdns-38.org, ns-1606.awsdns-08.co.uk, ns-447.awsdns-55.com, ns-716.awsdns-25.net |
| DNSSEC | no |
| Source | https://rdap.ca.fury.ca/rdap/domain/pj.ca |
pj.ca 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 ns-1334.awsdns-38.org is published for pj.ca in the registration record from https://rdap.ca.fury.ca/rdap/domain/pj.ca.
Nameserver ns-1606.awsdns-08.co.uk is published for pj.ca in the registration record from https://rdap.ca.fury.ca/rdap/domain/pj.ca.
Nameserver ns-447.awsdns-55.com is published for pj.ca in the registration record from https://rdap.ca.fury.ca/rdap/domain/pj.ca.
Nameserver ns-716.awsdns-25.net is published for pj.ca in the registration record from https://rdap.ca.fury.ca/rdap/domain/pj.ca.
pj.ca has 4 address records, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 65.8.131.129, 65.8.131.26, 65.8.131.36, 65.8.131.42 |
|---|---|
| AAAA | — |
| NS | ns-1334.awsdns-38.org, ns-1606.awsdns-08.co.uk, ns-447.awsdns-55.com, ns-716.awsdns-25.net |
| MX | pj-ca.mail.protection.outlook.com (10) Microsoft 365 |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.pj.ca is "v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]".
IPv4 address 65.8.131.129 answers for pj.ca at resolver 1.1.1.1:53.
IPv4 address 65.8.131.26 answers for pj.ca at resolver 1.1.1.1:53.
IPv4 address 65.8.131.36 answers for pj.ca at resolver 1.1.1.1:53.
IPv4 address 65.8.131.42 answers for pj.ca at resolver 1.1.1.1:53.
Mail exchanger pj-ca.mail.protection.outlook.com has preference 10. The host is recognised as Microsoft 365.
A random label under pj.ca also resolved, which means wildcard DNS is on.
pj.ca is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 65.8.131.129 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
The certificate for pj.ca is valid, with 94 days left and 6 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | pagesjaunes.ca |
| Valid from | 20 July 2026 |
| Valid until | 2 February 2027 |
| Days left | 94 |
| SAN count | 6 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.api.pagesjaunes.ca, *.pagesjaunes.ca, *.pj.ca, api.pagesjaunes.ca, pagesjaunes.ca, pj.ca.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
The homepage returned HTTP 403 in 8 ms. The target title is 41 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 8 ms |
| Title length | 41 yes |
| Quoted title | "ERROR: The request could not be satisfied" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| 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.
Family DNS for pj.ca 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 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 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.
pj.ca is placed in Frankfurt am Main, Germany.
pj.ca expires on 1 September 2029 according to https://rdap.ca.fury.ca/rdap/domain/pj.ca.
The registry did not return a person or a company for pj.ca. RDAP often redacts the registrant. The registrar on file is Webnames.ca Inc..
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.