apsgo.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 81 days left8 years oldTranco #640900
70
apsgo.com was registered on 26 Apr 2018 via Alibaba Cloud Computing (Beijing) Co., Ltd. and the registry expiry is 26 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/apsgo.com.
apsgo.com publishes 2 nameservers. DNSSEC is not signed.
apsgo.com has 1 IPv4 address (43.109.179.56). The geolocation database places 43.109.179.56 in Frankfurt am Main, Germany.
The TLS certificate from YR1 is valid and has 81 days left (TLS 1.3). The homepage answered HTTP 200.
No safety warning was recorded for apsgo.com in the checks that ran.
Domain · RDAP/WHOIS
apsgo.com was registered on 26 Apr 2018 via Alibaba Cloud Computing (Beijing) Co., Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/apsgo.com.
| Registered | since 26 Apr 2018 |
|---|---|
| Created | 26 April 2018 |
| Updated | 1 July 2026 |
| Expires | 26 April 2027 |
| Registrar | Alibaba Cloud Computing (Beijing) Co., Ltd. |
| Status | active |
| Nameservers | adriatic.ns.atrustdns.com, meru.ns.atrustdns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/apsgo.com |
Nameserver adriatic.ns.atrustdns.com is published for apsgo.com in the registration record from https://rdap.verisign.com/com/v1/domain/apsgo.com.
Nameserver meru.ns.atrustdns.com is published for apsgo.com in the registration record from https://rdap.verisign.com/com/v1/domain/apsgo.com.
DNS
apsgo.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 43.109.179.56 |
|---|---|
| AAAA | — |
| NS | adriatic.ns.atrustdns.com, meru.ns.atrustdns.com |
| MX | — |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at apsgo.com is "v=spf1 include:spf.qiye.aliyun.com -all".
IPv4 address 43.109.179.56 answers for apsgo.com at resolver 1.1.1.1:53.
A random label under apsgo.com also resolved, which means wildcard DNS is on.
Hosting and geo
apsgo.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 43.109.179.56 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for apsgo.com is valid, with 81 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | *.apsgo.com |
| Valid from | 22 October 2026 |
| Valid until | 20 January 2027 |
| Days left | 81 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.apsgo.com, apsgo.com.
Tech stack
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
On-page checks
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| 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 apsgo.com 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: dns a changed from 43.109.179.54 to 43.109.179.56.
- October 2026: geo city changed from empty to Frankfurt am Main.
- October 2026: geo country changed from empty to Germany.
Questions
Is apsgo.com 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 apsgo.com?
apsgo.com is placed in Frankfurt am Main, Germany.
When does apsgo.com expire?
apsgo.com expires on 26 April 2027 according to https://rdap.verisign.com/com/v1/domain/apsgo.com.
Who owns apsgo.com?
The registry did not return a person or a company for apsgo.com. RDAP often redacts the registrant. The registrar on file is Alibaba Cloud Computing (Beijing) Co., Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/apsgo.com at 2026-10-30T13:45:03Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:45:03Z
- TLS source tls:443 at 2026-10-30T13:45:03Z
- HTTP source https://apsgo.com/ at 2026-10-30T13:45:03Z
- Tech source wappalyzergo at 2026-10-30T13:45:03Z
- Geo source db-ip at 2026-10-30T13:45:03Z
- Safety source family DNS and local lists at 2026-10-30T13:45:03Z
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.