pinoytambayan.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 71 days left6 years old
45
pinoytambayan.org was registered on 16 Jun 2020 via NameCheap, Inc. and the registry expiry is 16 Jun 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/pinoytambayan.org.
pinoytambayan.org publishes 2 nameservers. DNSSEC is not signed.
pinoytambayan.org has 2 IPv4 addresses (104.21.42.224, 172.67.167.33) and 2 IPv6 addresses (2606:4700:3031::ac43:a721, 2606:4700:3035::6815:2ae0). The geolocation database places 104.21.42.224 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 71 days left (TLS 1.3).
Domain · RDAP/WHOIS
pinoytambayan.org was registered on 16 Jun 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/pinoytambayan.org.
| Registered | since 16 Jun 2020 |
|---|---|
| Created | 16 June 2020 |
| Updated | 12 August 2026 |
| Expires | 16 June 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | izabella.ns.cloudflare.com, mustafa.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/pinoytambayan.org |
pinoytambayan.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.
Nameserver izabella.ns.cloudflare.com is published for pinoytambayan.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/pinoytambayan.org.
Nameserver mustafa.ns.cloudflare.com is published for pinoytambayan.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/pinoytambayan.org.
DNS
pinoytambayan.org has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.42.224, 172.67.167.33 |
|---|---|
| AAAA | 2606:4700:3031::ac43:a721, 2606:4700:3035::6815:2ae0 |
| NS | izabella.ns.cloudflare.com, mustafa.ns.cloudflare.com |
| MX | route1.mx.cloudflare.net (10), route3.mx.cloudflare.net (18), route2.mx.cloudflare.net (91) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at pinoytambayan.org is "v=spf1 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.pinoytambayan.org is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.21.42.224 answers for pinoytambayan.org at resolver 1.1.1.1:53.
IPv4 address 172.67.167.33 answers for pinoytambayan.org at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:a721 answers for pinoytambayan.org at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:2ae0 answers for pinoytambayan.org at resolver 1.1.1.1:53.
Mail exchanger route1.mx.cloudflare.net has preference 10.
Mail exchanger route3.mx.cloudflare.net has preference 18.
Mail exchanger route2.mx.cloudflare.net has preference 91.
Hosting and geo
pinoytambayan.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.42.224 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for pinoytambayan.org is valid, with 71 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | pinoytambayan.org |
| Valid from | 13 October 2026 |
| Valid until | 11 January 2027 |
| Days left | 71 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.pinoytambayan.org, pinoytambayan.org.
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://pinoytambayan.org/": context deadline exceeded
Security
Family DNS for pinoytambayan.org is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for pinoytambayan.org. 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 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 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 pinoytambayan.org safe?
Cloudflare family DNS returned a block for pinoytambayan.org. That resolver covers adult and malware names.
Who hosts pinoytambayan.org?
pinoytambayan.org is placed in Toronto, Canada.
When does pinoytambayan.org expire?
pinoytambayan.org expires on 16 June 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/pinoytambayan.org.
Who owns pinoytambayan.org?
The registry did not return a person or a company for pinoytambayan.org. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/pinoytambayan.org at 2026-10-30T15:03:11Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:03:11Z
- TLS source tls:443 at 2026-10-30T15:03:11Z
- HTTP source https://pinoytambayan.org/ at 2026-10-30T15:03:11Z
- Tech source not available at 2026-10-30T15:03:11Z
- Geo source db-ip at 2026-10-30T15:03:11Z
- Safety source family DNS and local lists at 2026-10-30T15:03:11Z
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.