worldsecurity.ae is registered with Etisalat and is hosted on AS46606 Unified Layer in United States of America. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed worldsecurity.ae. Refresh the analysis to check again.
11 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| worldsecurity.site | Other extension | 13 Nov 2026 | Checking… | Report → |
| worldsecurity.pe | Other extension | 5 Oct 2026 | Checking… | Report → |
| wrldsecurity.net | Typo | 25 Aug 2026 | Checking… | Report → |
| worldsecurityfze.com | Keyword added | 28 Sept 2026 | Checking… | Report → |
| worldsecurity-inc.com | Keyword added | 3 Nov 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is worldsecurity.ae’s name taken on other extensions?
Every IP address worldsecurity.ae resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| worldsecurity.ae | 162.241.253.219 | 21600 |
| Host | Mail server | TTL |
|---|---|---|
| worldsecurity.ae | 0 worldsecurity-ae.mail.protection.outlook.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| worldsecurity.ae | ns1.etisalatdomains.ae | 21600 |
| worldsecurity.ae | ns2.etisalatdomains.ae | 21600 |
| worldsecurity.ae | ns3.etisalatdomains.ae | 21600 |
| worldsecurity.ae | ns4.etisalatdomains.ae | 21600 |
| Host | Text | TTL |
|---|---|---|
| worldsecurity.ae | "_globalsign-domain-verification=ET6uJErGZNBKWD7-SbCvkvYTPIhTiGB11Q61isxStI" | 3600 |
| worldsecurity.ae | "google-site-verification=iWrwb9zJUTHLbNW1cEBKx10HSdiOuY2K6VoPyscEsBU" | 3600 |
| worldsecurity.ae | "MS=ms13003660" | 3600 |
| worldsecurity.ae | "MS=ms41832984" | 3600 |
| worldsecurity.ae | "v=spf1 ip4:20.74.131.131 a:mailt1.dpworld.ae a:mailt2.dpworld.ae include:spf.protection.outlook.com -all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| worldsecurity.ae | a2e-ib-dns-gm.etisalat.ae domains.etisalat.ae 2021032551 10800 3600 2419200 900 | 21600 |
Other domains served from 162.241.253.219. Normal for shared hosting and CDNs.
No reviews yet. Used worldsecurity.ae? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
worldsecurity.ae has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
worldsecurity.ae is registered through Etisalat. See WHOIS →
worldsecurity.ae is served from 1 IP address, mainly on AS46606 Unified Layer in United States of America. See Hosting →
Raw registry data for worldsecurity.ae. May be redacted by privacy services.
Domain Name: worldsecurity.ae Registrar ID: Etisalat Registrar Name: Etisalat Status: ok Registrant Contact ID: ETSLT279288-R Registrant Contact Name: DP World UAE Region FZE Registrant Contact Email: Visit whois.aeda.net.ae for Web based WhoIs Registrant Contact Organisation: DP World UAE Region FZE Tech Contact ID: ETSLT279289-C Tech Contact Name: DP World UAE Region FZE Tech Contact Email: Visit whois.aeda.net.ae for Web based WhoIs Tech Contact Organisation: DP World UAE Region FZE Name Server: ns1.etisalatdomains.ae Name Server: ns2.etisalatdomains.ae
The first response from http://www.worldsecurity.ae, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with worldsecurity.ae. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.