xxgasm.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 26 days left10 years oldTranco #118254
40
xxgasm.com was registered on 11 Apr 2016 via NameCheap, Inc. and the registry expiry is 11 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/xxgasm.com.
xxgasm.com publishes 2 nameservers. DNSSEC is signed.
xxgasm.com has 1 IPv4 address (173.208.199.194). The geolocation database places 173.208.199.194 in Kansas City, United States.
The TLS certificate from YR1 is valid and has 26 days left (TLS 1.2).
Tech detection named Nginx. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
xxgasm.com was registered on 11 Apr 2016 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/xxgasm.com.
| Registered | since 11 Apr 2016 |
|---|---|
| Created | 11 April 2016 |
| Updated | 27 August 2026 |
| Expires | 11 April 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | pdns1.registrar-servers.com, pdns2.registrar-servers.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/xxgasm.com |
xxgasm.com 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 pdns1.registrar-servers.com is published for xxgasm.com in the registration record from https://rdap.verisign.com/com/v1/domain/xxgasm.com.
Nameserver pdns2.registrar-servers.com is published for xxgasm.com in the registration record from https://rdap.verisign.com/com/v1/domain/xxgasm.com.
DNS
xxgasm.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 173.208.199.194 |
|---|---|
| AAAA | — |
| NS | pdns1.registrar-servers.com, pdns2.registrar-servers.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 173.208.199.194 answers for xxgasm.com at resolver 1.1.1.1:53.
Hosting and geo
xxgasm.com is placed in Kansas City, United States by the local geolocation database (db-ip).
| Address | 173.208.199.194 |
|---|---|
| Country | United States |
| City | Kansas City |
| Source | db-ip |
SSL/TLS
The certificate for xxgasm.com is valid, with 26 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | xxgasm.com |
| Valid from | 29 August 2026 |
| Valid until | 27 November 2026 |
| Days left | 26 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: www.xxgasm.com, xxgasm.com.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- Nginx · Web servers, Reverse proxies
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 403 in 124 ms. The target title is 13 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 124 ms |
| Title length | 13 yes |
| Quoted title | "403 Forbidden" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| 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 xxgasm.com 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 xxgasm.com. 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 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 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
- October 2026: geo city changed from empty to Kansas City.
- October 2026: geo country changed from empty to United States.
Questions
Is xxgasm.com safe?
Cloudflare family DNS returned a block for xxgasm.com. That resolver covers adult and malware names.
Who hosts xxgasm.com?
xxgasm.com is placed in Kansas City, United States.
When does xxgasm.com expire?
xxgasm.com expires on 11 April 2027 according to https://rdap.verisign.com/com/v1/domain/xxgasm.com.
Who owns xxgasm.com?
The registry did not return a person or a company for xxgasm.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/xxgasm.com at 2026-10-30T14:21:00Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:21:00Z
- TLS source tls:443 at 2026-10-30T14:21:00Z
- HTTP source https://xxgasm.com/ at 2026-10-30T14:21:00Z
- Tech source wappalyzergo at 2026-10-30T14:21:00Z
- Geo source db-ip at 2026-10-30T14:21:00Z
- Safety source family DNS and local lists at 2026-10-30T14:21:00Z
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.