domain/designersperfumesa.info
- 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 archivedesignersperfumesa.info was registered in December 2025 with NameSilo, and is due to expire in December 2026. Its website was online at the last check, served from Automattic's network. designersperfumesa.info doesn't receive email: it publishes no mail servers. The website presents it as Designers Perfume SA (perfume retailer).
Based on what we observed, its registration expires in 13 days.
| Type | Value |
|---|---|
| A | 192.0.78.24 AS2635 · Automattic, Inc · US |
| A | 192.0.78.25 AS2635 · Automattic, Inc · US |
| NS | ns1.wordpress.com |
| NS | ns2.wordpress.com |
| NS | ns3.wordpress.com |
| TXT | v=spf1 include:_spf.wpcloud.com ~all |
| DMARC | v=DMARC1;p=none; |
| SOA | ns1.wordpress.com hostmaster.wordpress.com 2026040801 |
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.
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. designersperfumesa.info is registered through NameSilo. The website presents itself as Designers Perfume SA; that is the site's own claim, not a verified owner.
designersperfumesa.info was registered on 5 Dec 2025, making it 11 months old.
The registry lists 5 Dec 2026 as the expiry date, 14 days from now. Most domains renew automatically before then.
designersperfumesa.info's website is served from Automattic's network.
No one: designersperfumesa.info publishes no MX records, so it can't receive email.
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.