domain/virgolinks.com
- 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 archivevirgolinks.com was registered in December 2016 with GoDaddy.com, and is due to expire in December 2027. Its website was online at the last check, served from Contabo's network. Email for virgolinks.com is handled by Microsoft 365. The website presents it as Virgo Link (non-emergency medical transportation).
Registered 10 years ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 178.18.254.193 AS51167 · Contabo GmbH · DE |
| MX | 0 virgolinks-com.mail.protection.outlook.com |
| NS | ns67.domaincontrol.com |
| NS | ns68.domaincontrol.com |
| TXT | kmcbvi6bco8rsifeheianlh95a |
| TXT | v=spf1 include:spf.protection.outlook.com -all |
| SOA | ns67.domaincontrol.com dns.jomax.net 2026101502 |
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 1 page.
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. virgolinks.com is registered through GoDaddy.com. The website presents itself as Virgo Link; that is the site's own claim, not a verified owner.
virgolinks.com was registered on 29 Dec 2016, making it 9 years old.
The registry lists 29 Dec 2027 as the expiry date, 403 days from now. Most domains renew automatically before then.
virgolinks.com's website is served from Contabo's network.
Email for virgolinks.com is handled by Microsoft 365, according to its MX records.
It was up when we last checked, 4 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.