domain/aandnscents.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 archiveaandnscents.com was registered in November 2025 with OwnRegistrar, and is due to expire in November 2026. Its website was online at the last check, served from Amazon.com's network. aandnscents.com doesn't receive email: it publishes no mail servers. The website presents it as A & N (arabic perfume and ittar business).
Based on what we observed, its registration expires in 7 days and it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 216.198.79.65 AS16509 · Amazon.com, Inc. · US |
| A | 64.29.17.65 AS16509 · Amazon.com, Inc. · US |
| NS | ns1.vercel-dns.com |
| NS | ns2.vercel-dns.com |
| CAA | 0 issue "letsencrypt.org" |
| CAA | 0 issue "pki.goog" |
| CAA | 0 issue "sectigo.com" |
| SOA | ns1.vercel-dns.com hostmaster.nsone.net 1764352379 |
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.
No public prices on the pages we read.
Every value is quoted from the page linked beside it. Read from 4 pages.
Most registries now keep the registrant's details private, and whois.is doesn't show them. aandnscents.com is registered through OwnRegistrar. The website presents itself as A & N; that is the site's own claim, not a verified owner.
aandnscents.com was registered on 28 Nov 2025, making it 11 months old.
The registry lists 28 Nov 2026 as the expiry date, 7 days from now. Most domains renew automatically before then.
aandnscents.com's website is served from Amazon.com's network.
No one: aandnscents.com publishes no MX records, so it can't receive email.
It was up when we last checked, 21 hours ago (20 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.