MXLIST.NET - www.danskahen.com
Search for IP or hostnames:
www.danskahen.com checked at 2025-10-25T02:35:58.434Z 251ms 75/75/75 100% R:8www.danskahen.com
| CNAME | hc.hms-gtm.com | ||||||
| MX | . | ||||||
| NS | ns1.afternic.com | ||||||
| A | 2603:5:2126::45 🇺🇸 GODADDY-DNS | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS | ||||||
| PTR | ns1.afternic.com | ||||||
| NS | ns2.afternic.com | ||||||
| A | 2603:5:2226::45 🇺🇸 GODADDY-DNS | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 13.248.169.48🇺🇸 Amazon | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
danskahen.com
| NS | ns1.shopco.com | ||||||
| NS | ns2.shopco.com | ||||||
| NS | ns3.shopco.com | ||||||
| MX | mx.danskahen.com.cust.b.hostedemail.com | ||||||
| A | 64.68.36.10 | ||||||
Starts with same word
Starts similarily
AI analysis
www.danskahen.com resolves to two IPs: 13.248.169.48 and 76.223.54.146.
other host names for instance godirections.com, slickwebsites.com, cardback.org, dc-52c6d0b9.importantquestions.net and thedesignmuseum.com share IP numbers with www.danskahen.com.
www.danskahen.com is delegated to two name servers: ns1.afternic.com and ns2.afternic.com.
www.danskahen.com shares the same name server setup as other domains, for example www.afghantelecom.com, gify.me, cnz.betpay.net, uaf.io and butiqa.com.
Host names with two IP numbers:
ns1.afternic.com points to 2603:5:2126::45 and 97.74.98.69
ns2.afternic.com points to 2603:5:2226::45 and 173.201.66.69
www.danskahen.com is handled by a single mail server, ..
www.danskahen.com shares the same mail server setup as other domains, for instance srtyle.com, vanderstroom.nl, elinkups.com, youxp.com and bctrading.com.
www.danskahen.com shares some mail servers with other domains, at least partially, for instance jade-selection.de and pcprotectionplus.com.pt.
these mail servers are commonly used alongside noemail.invalid.