purewatch.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 42 days left2 years old
70
purewatch.net was registered on 24 May 2024 via TurnCommerce, Inc. DBA NameBright.com and the registry expiry is 24 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/purewatch.net.
purewatch.net publishes 2 nameservers. DNSSEC is not signed.
purewatch.net has 1 IPv4 address (103.224.212.217). The geolocation database places 103.224.212.217 in Beaumaris, Australia.
The TLS certificate from YE2 is valid and has 42 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for purewatch.net in the checks that ran.
Domain · RDAP/WHOIS
purewatch.net was registered on 24 May 2024 via TurnCommerce, Inc. DBA NameBright.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/purewatch.net.
| Registered | since 24 May 2024 |
|---|---|
| Created | 24 May 2024 |
| Updated | 30 April 2026 |
| Expires | 24 May 2027 |
| Registrar | TurnCommerce, Inc. DBA NameBright.com |
| Status | active |
| Nameservers | ns15.abovedomains.com, ns16.abovedomains.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/purewatch.net |
Nameserver ns15.abovedomains.com is published for purewatch.net in the registration record from https://rdap.verisign.com/net/v1/domain/purewatch.net.
Nameserver ns16.abovedomains.com is published for purewatch.net in the registration record from https://rdap.verisign.com/net/v1/domain/purewatch.net.
DNS
purewatch.net has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 103.224.212.217 |
|---|---|
| AAAA | — |
| NS | ns15.abovedomains.com, ns16.abovedomains.com |
| MX | park-mx.above.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at purewatch.net is "v=spf1 ip6:fdcf:abda:4154::/48 -all".
IPv4 address 103.224.212.217 answers for purewatch.net at resolver 1.1.1.1:53.
Mail exchanger park-mx.above.com has preference 10.
A random label under purewatch.net also resolved, which means wildcard DNS is on.
Hosting and geo
purewatch.net is placed in Beaumaris, Australia by the local geolocation database (db-ip).
| Address | 103.224.212.217 |
|---|---|
| Country | Australia |
| City | Beaumaris |
| Source | db-ip |
SSL/TLS
The certificate for purewatch.net is valid, with 42 days left and 68 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | chamelephon.com |
| Valid from | 13 September 2026 |
| Valid until | 12 December 2026 |
| Days left | 42 |
| SAN count | 68 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.agent-ultra.jp, *.beespokekitchens.co.uk, *.chamelephon.com, *.crewscont.ol.net.au, *.crm.elitefastenersinc.com, *.curriculumtopicstudy.org, *.elitefastenersinc.com, *.elranchohouston.com, *.faqmceatdamf.com, *.finance-broker.com.au, *.fmh-gmbh.de, *.highfiveanime.shop, *.kimsthaimassage.com, *.knxcont.ol.net.au, *.ledilizia.it, *.lime.elitefastenersinc.com, *.mail3.elitefastenersinc.com, *.military-fasteners.elitefastenersinc.com, *.northbrookfarmstay.com.au, *.ns.elitefastenersinc.com, *.oceanfrontunits.com.au, *.ol.net.au, *.owa.elitefastenersinc.com, *.portal.elitefastenersinc.com, *.postmaster.agent-ultra.jp, *.purewatch.net, *.rds1.elitefastenersinc.com, *.rdweb.elitefastenersinc.com, *.remote.elitefastenersinc.com, *.sitemaps.purewatch.net, *.tiranaeyc2022.al, *.vinciadesso.it, *.wildcard.elitefastenersinc.com, *.ww16.chamelephon.com, *.ww16.northbrookfarmstay.com.au, *.ww16.zaviak.com, *.ww25.agent-ultra.jp, *.ww25.elranchohouston.com, *.ww25.kimsthaimassage.com, *.ww25.northbrookfarmstay.com.au, *.ww25.purewatch.net, *.ww38.agent-ultra.jp, *.ww38.highfiveanime.shop, *.ww38.oceanfrontunits.com.au, *.ww38.purewatch.net, *.www.finance-broker.com.au, *.zaviak.com, *.zenzar.co, agent-ultra.jp, beespokekitchens.co.uk, chamelephon.com, curriculumtopicstudy.org, elitefastenersinc.com, elranchohouston.com, faqmceatdamf.com, finance-broker.com.au, fmh-gmbh.de, highfiveanime.shop, kimsthaimassage.com, ledilizia.it, northbrookfarmstay.com.au, oceanfrontunits.com.au, ol.net.au, purewatch.net, tiranaeyc2022.al, vinciadesso.it, zaviak.com, zenzar.co.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- Apache HTTP Server · Web servers
Apache HTTP Server is filed under Web servers.
On-page checks
The homepage returned HTTP 200 in 465 ms. The target title is 13 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 465 ms |
| Title length | 13 yes |
| Quoted title | "purewatch.net" |
| Meta description | "Find information, resources and relevant links for purewatch.net. This domain may be for sale." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 2 |
| 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 purewatch.net 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 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.
Change history
- October 2026: tls issuer changed from empty to YE2.
- October 2026: tls not_after changed from empty to 2026-12-12T07:38:00Z.
- October 2026: tls protocol changed from empty to TLS 1.3.
- October 2026: tls valid changed from false to true.
- October 2026: http status_class changed from empty to 2xx.
- October 2026: tech added Apache HTTP Server.
- October 2026: geo city changed from empty to Beaumaris.
- October 2026: geo country changed from empty to Australia.
Questions
Is purewatch.net 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 purewatch.net?
purewatch.net is placed in Beaumaris, Australia.
When does purewatch.net expire?
purewatch.net expires on 24 May 2027 according to https://rdap.verisign.com/net/v1/domain/purewatch.net.
Who owns purewatch.net?
The registry did not return a person or a company for purewatch.net. RDAP often redacts the registrant. The registrar on file is TurnCommerce, Inc. DBA NameBright.com.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/purewatch.net at 2026-10-30T14:55:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:55:07Z
- TLS source tls:443 at 2026-10-30T14:55:07Z
- HTTP source https://purewatch.net/ at 2026-10-30T14:55:07Z
- Tech source wappalyzergo at 2026-10-30T14:55:07Z
- Geo source db-ip at 2026-10-30T14:55:07Z
- Safety source family DNS and local lists at 2026-10-30T14:55:07Z
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.