domain/sla-medical.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 archivesla-medical.com was registered in September 2026 with GoDaddy.com, and is due to expire in September 2031. Its website was online at the last check, served from Amazon.com's network. sla-medical.com doesn't receive email: it publishes no mail servers. The website presents it as SLA Medical (medical).
Based on what we observed, it was registered within the last year.
| Type | Value |
|---|---|
| A | 13.248.243.5 AS16509 · Amazon.com, Inc. · US |
| A | 76.223.105.230 AS16509 · Amazon.com, Inc. · US |
| NS | ns43.domaincontrol.com |
| NS | ns44.domaincontrol.com |
| DMARC | v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:[email protected]; |
| SOA | ns43.domaincontrol.com dns.jomax.net 2026090302 |
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.
None stated on the pages we read.
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. sla-medical.com is registered through GoDaddy.com. The website presents itself as SLA Medical; that is the site's own claim, not a verified owner.
sla-medical.com was registered on 4 Sept 2026, making it 2 months old.
The registry lists 4 Sept 2031 as the expiry date, 1748 days from now. Most domains renew automatically before then.
sla-medical.com's website is served from Amazon.com's network.
No one: sla-medical.com publishes no MX records, so it can't receive email.
It was up when we last checked, 14 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.