domain/medalert.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 archivemedalert.ng was registered in August 2025 with Leanna Hosting Solutions, and is due to expire in August 2028. Its website was online at the last check, served from InMotion Hosting's network. Email for medalert.ng is handled by medalert.ng.
Registered 1 year ago. The website responds, SPF and DMARC are published and the certificate is trusted.
The last check failed. The operation was aborted due to timeout. What follows is the most recent evidence we hold.
| Type | Value |
|---|---|
| A | 209.182.202.35 AS22611 · InMotion Hosting, Inc. · US |
| MX | 0 mail.medalert.ng |
| NS | ns1.leanna.ng |
| NS | ns2.leanna.ng |
| TXT | v=spf1 +mx +a +ip4:209.182.202.35 +include:relay.mailchannels.net ~all |
| DMARC | v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s;pct=100;fo=0;rf=afrf;ri=86400 |
| SOA | ns1.leanna.ng admin.broaddrive.net 2025101002 |
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.
Read from the homepage's code and server headers. Sites can hide what they use, so this list may be incomplete.
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.
Most registries now keep the registrant's details private, and whois.is doesn't show them. medalert.ng is registered through Leanna Hosting Solutions.
medalert.ng was registered on 4 Aug 2025, making it 1 year old.
The registry lists 4 Aug 2028 as the expiry date, 622 days from now. Most domains renew automatically before then.
medalert.ng's website is served from InMotion Hosting's network.
Email for medalert.ng is handled by medalert.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.