audionews.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
audionews.org was registered on 25 May 2002 via Register.com - Network Solutions, LLC and the registry expiry is 25 May 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/audionews.org.
audionews.org publishes 2 nameservers. DNSSEC is not signed.
audionews.org has 3 IPv4 addresses (104.26.14.74, 104.26.15.74, 172.67.74.54). The geolocation database places 104.26.14.74 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 35 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, PHP, jQuery, jQuery CDN and jQuery UI. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for audionews.org in the checks that ran.
audionews.org was registered on 25 May 2002 via Register.com - Network Solutions, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/audionews.org.
| Registered | since 25 May 2002 |
|---|---|
| Created | 25 May 2002 |
| Updated | 11 August 2026 |
| Expires | 25 May 2027 |
| Registrar | Register.com - Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | lina.ns.cloudflare.com, rob.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/audionews.org |
audionews.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 lina.ns.cloudflare.com is published for audionews.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/audionews.org.
Nameserver rob.ns.cloudflare.com is published for audionews.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/audionews.org.
audionews.org has 3 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.14.74, 104.26.15.74, 172.67.74.54 |
|---|---|
| AAAA | — |
| NS | lina.ns.cloudflare.com, rob.ns.cloudflare.com |
| MX | mx.yandex.net (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at audionews.org is "v=spf1 a mx include:spf.smtp.bz ~all".
The DMARC text record at _dmarc.audionews.org is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.26.14.74 answers for audionews.org at resolver 1.1.1.1:53.
IPv4 address 104.26.15.74 answers for audionews.org at resolver 1.1.1.1:53.
IPv4 address 172.67.74.54 answers for audionews.org at resolver 1.1.1.1:53.
Mail exchanger mx.yandex.net has preference 10.
audionews.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.14.74 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for audionews.org is valid, with 35 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | audionews.org |
| Valid from | 6 September 2026 |
| Valid until | 5 December 2026 |
| Days left | 35 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.audionews.org, audionews.org.
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
PHP is filed under Programming languages.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
jQuery UI is filed under JavaScript libraries.
The homepage returned HTTP 200 in 209 ms. The target title is 21 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 209 ms |
| Title length | 21 yes |
| Quoted title | "Home :: Audionews.org" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 19 |
| Images | 6 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for audionews.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.
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 5 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
audionews.org is placed in Toronto, Canada.
audionews.org expires on 25 May 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/audionews.org.
The registry did not return a person or a company for audionews.org. RDAP often redacts the registrant. The registrar on file is Register.com - Network Solutions, 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.