abcwagering.ag
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 73 days left13 years old
70
abcwagering.ag was registered on 7 Feb 2013 via GoDaddy.com, LLC and the registry expiry is 7 Feb 2028. WHOIS data came from a WHOIS query because RDAP is not published for this TLD.
abcwagering.ag publishes 2 nameservers. DNSSEC is not signed.
abcwagering.ag has 2 IPv4 addresses (104.18.37.155, 172.64.150.101) and 2 IPv6 addresses (2606:4700:4403::ac40:9665, 2606:4700:4406::6812:259b). The geolocation database places 104.18.37.155 in Toronto, Canada.
The TLS certificate from YE2 is valid and has 73 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, BootstrapCDN, Cloudflare, HSTS, RequireJS, jQuery and jQuery CDN. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for abcwagering.ag in the checks that ran.
Domain · RDAP/WHOIS
abcwagering.ag was registered on 7 Feb 2013 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from whois://whois.nic.ag.
| Registered | since 7 Feb 2013 |
|---|---|
| Created | 7 February 2013 |
| Updated | 11 August 2026 |
| Expires | 7 February 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | clientdeleteprohibited, clientrenewprohibited, clienttransferprohibited, clientupdateprohibited |
| Nameservers | april.ns.cloudflare.com, joel.ns.cloudflare.com |
| DNSSEC | unknown |
| Source | whois://whois.nic.ag |
RDAP is not available for .ag
Nameserver april.ns.cloudflare.com is published for abcwagering.ag in the registration record from whois://whois.nic.ag.
Nameserver joel.ns.cloudflare.com is published for abcwagering.ag in the registration record from whois://whois.nic.ag.
DNS
abcwagering.ag has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.18.37.155, 172.64.150.101 |
|---|---|
| AAAA | 2606:4700:4403::ac40:9665, 2606:4700:4406::6812:259b |
| NS | april.ns.cloudflare.com, joel.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.18.37.155 answers for abcwagering.ag at resolver 1.1.1.1:53.
IPv4 address 172.64.150.101 answers for abcwagering.ag at resolver 1.1.1.1:53.
IPv6 address 2606:4700:4403::ac40:9665 answers for abcwagering.ag at resolver 1.1.1.1:53.
IPv6 address 2606:4700:4406::6812:259b answers for abcwagering.ag at resolver 1.1.1.1:53.
Hosting and geo
abcwagering.ag is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.18.37.155 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for abcwagering.ag is valid, with 73 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | abcwagering.ag |
| Valid from | 14 October 2026 |
| Valid until | 12 January 2027 |
| Days left | 73 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.abcwagering.ag, abcwagering.ag.
Tech stack
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- BootstrapCDN · CDN
- Cloudflare · CDN
- HSTS · Security
- RequireJS · JavaScript frameworks
- jQuery · JavaScript libraries
- jQuery CDN · CDN
Bootstrap is filed under UI frameworks.
BootstrapCDN is filed under CDN.
Cloudflare is filed under CDN.
HSTS is filed under Security.
RequireJS is filed under JavaScript frameworks.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 356 ms. The target title is 22 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 356 ms |
| Title length | 22 yes |
| Quoted title | ".:www.abcwagering.ag:." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 1 |
| 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.
Security
Family DNS for abcwagering.ag 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 | yes |
| 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 0 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.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is abcwagering.ag 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 abcwagering.ag?
abcwagering.ag is placed in Toronto, Canada.
When does abcwagering.ag expire?
abcwagering.ag expires on 7 February 2028 according to whois://whois.nic.ag.
Who owns abcwagering.ag?
The registry did not return a person or a company for abcwagering.ag. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source whois://whois.nic.ag at 2026-10-30T13:30:54Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:30:54Z
- TLS source tls:443 at 2026-10-30T13:30:54Z
- HTTP source https://abcwagering.ag/ at 2026-10-30T13:30:54Z
- Tech source wappalyzergo at 2026-10-30T13:30:54Z
- Geo source db-ip at 2026-10-30T13:30:54Z
- Safety source family DNS and local lists at 2026-10-30T13:30:54Z
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.