domain/citylink.ng
- Registration data
RDAP - DNS records
A, AAAA, MX, NS, TXT, CAA, SOA - Email policy
_dmarc - TLS certificate
port 443 - Website snapshot
HTTP - Comparing with history
whois.is archive
RDAPA, AAAA, MX, NS, TXT, CAA, SOA_dmarcport 443HTTPwhois.is archivecitylink.ng was registered in October 2026 with TRUEHOST CLOUD, and is due to expire in October 2027. Its website was online at the last check, served from Truehost Cloud's network. Email for citylink.ng is handled by citylink.ng. The website presents it as Citylink (wallet and vtu platform).
Based on what we observed, it was registered within the last year.
The last check failed. RDAP returned 502 for citylink.ng. What follows is the most recent evidence we hold.
| Type | Value |
|---|---|
| A | 102.203.116.14 AS329278 · Truehost Cloud Limited · KE |
| MX | 0 citylink.ng |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| NS | ns3.cloudoon.com |
| TXT | v=spf1 ip4:102.203.116.13 +a +mx include:_spf.truehostcloud.com ~all |
| DMARC | v=DMARC1; p=none; |
| SOA | ns1.cloudoon.com root.das131.truehost.cloud 2026102805 |
A network is whoever runs the servers behind the address. With a CDN such as Cloudflare in front, that is the CDN, not the company hosting the site behind it.
We didn't recognise any technology on the homepage.
No public prices on the pages we read.
Every value is quoted from the page linked beside it. Read from 2 pages.
First observation recorded. Every change from here on is preserved and shown here.
Most registries now keep the registrant's details private, and whois.is doesn't show them. citylink.ng is registered through TRUEHOST CLOUD. The website presents itself as Citylink; that is the site's own claim, not a verified owner.
citylink.ng was registered on 27 Oct 2026, making it 24 days old.
The registry lists 27 Oct 2027 as the expiry date, 341 days from now. Most domains renew automatically before then.
citylink.ng's website is served from Truehost Cloud's network.
Email for citylink.ng is handled by citylink.ng, according to its MX records.
It was up when we last checked, 23 hours ago (20 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.