camegle.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
camegle.net was registered on 24 Oct 2018 via GoDaddy.com, LLC and the registry expiry is 24 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/camegle.net.
camegle.net publishes 4 nameservers. DNSSEC is not signed.
camegle.net has 2 IPv4 addresses (13.219.111.5, 52.87.93.247). The geolocation database places 13.219.111.5 in Ashburn, United States.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 90 days left (TLS 1.2).
camegle.net was registered on 24 Oct 2018 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/net/v1/domain/camegle.net.
| Registered | since 24 Oct 2018 |
|---|---|
| Created | 24 October 2018 |
| Updated | 25 October 2025 |
| Expires | 24 October 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns-1015.awsdns-62.net, ns-1045.awsdns-02.org, ns-1772.awsdns-29.co.uk, ns-267.awsdns-33.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/camegle.net |
camegle.net 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.
camegle.net 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.
camegle.net 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.
camegle.net 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 ns-1015.awsdns-62.net is published for camegle.net in the registration record from https://rdap.verisign.com/net/v1/domain/camegle.net.
Nameserver ns-1045.awsdns-02.org is published for camegle.net in the registration record from https://rdap.verisign.com/net/v1/domain/camegle.net.
Nameserver ns-1772.awsdns-29.co.uk is published for camegle.net in the registration record from https://rdap.verisign.com/net/v1/domain/camegle.net.
Nameserver ns-267.awsdns-33.com is published for camegle.net in the registration record from https://rdap.verisign.com/net/v1/domain/camegle.net.
camegle.net has 2 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 13.219.111.5, 52.87.93.247 |
|---|---|
| AAAA | — |
| NS | ns-1015.awsdns-62.net, ns-1045.awsdns-02.org, ns-1772.awsdns-29.co.uk, ns-267.awsdns-33.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 13.219.111.5 answers for camegle.net at resolver 1.1.1.1:53.
IPv4 address 52.87.93.247 answers for camegle.net at resolver 1.1.1.1:53.
camegle.net is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 13.219.111.5 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
The certificate for camegle.net is valid, with 90 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | camegle.net |
| Valid from | 16 July 2026 |
| Valid until | 29 January 2027 |
| Days left | 90 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: camegle.net, www.camegle.net.
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://live.camegle.net:443/": tls: failed to verify certificate: x509: certificate is valid for ingress.local, not live.camegle.net
Family DNS for camegle.net 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 camegle.net. 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.
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 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.
Cloudflare family DNS returned a block for camegle.net. That resolver covers adult and malware names.
camegle.net is placed in Ashburn, United States.
camegle.net expires on 24 October 2027 according to https://rdap.verisign.com/net/v1/domain/camegle.net.
The registry did not return a person or a company for camegle.net. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
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.