internetcars.ru - robtex.com

internetcars.ru

DNSSEC⚠️ Not signed
A20.101.75.154πŸ‡³πŸ‡± Microsoft20.64.0.0/10
NSns1-04.azure-dns.com ⭐
A2603:1061:0:700::4πŸ‡ΊπŸ‡Έ Microsoft2603:1000::/25 MICROSOFT
PTRns1-04.azure-dns.com
A13.107.236.4πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
PTRns1-04.azure-dns.com
NSns2-04.azure-dns.net
A2620:1ec:8ec:700::4πŸ‡ΊπŸ‡Έ Microsoft2620:1ec::/36 MICROSOFT
PTRns2-04.azure-dns.net
A150.171.21.4πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
PTRns2-04.azure-dns.net
NSns3-04.azure-dns.org ⚠️ Not in parent delegation
A2a01:111:4000:700::4πŸ‡¬πŸ‡§ Microsoft2a01:111:4000::/36
PTRns3-04.azure-dns.org
A204.14.183.4πŸ‡ΊπŸ‡Έ Microsoft204.14.180.0/22
PTRns3-04.azure-dns.org
NSns4-04.azure-dns.info ⚠️ Not in parent delegation
A2620:1ec:bda:700::4πŸ‡ΊπŸ‡Έ Microsoft2620:1ec::/36 MICROSOFT
PTRns4-04.azure-dns.info
A208.84.5.4πŸ‡ΊπŸ‡Έ Microsoft208.84.0.0/21 MICROSOFT
PTRns4-04.azure-dns.info
MXmx.yandex.net ⭐
A2a02:6b8::311πŸ‡·πŸ‡Ί TELETECH2a02:6b8::/32 Yandex network
PTRmxfront.stable.qloud-b.yandex.net
A77.88.21.249πŸ‡·πŸ‡Ί TELETECH77.88.0.0/18 Yandex enterprise network
PTRmxfront.stable.qloud-b.yandex.net
TXT_globalsign-domain-verification=_rQtZFWAdAL4_NRaQSwbX_yLlPLHDLz0xkPxKcFXpI
SOAns1-04.azure-dns.comazuredns-hostmaster@microsoft.com serial=1

ru

DNSSECπŸ”’ Signed (DS record present)
NSa.dns.ripn.net ⭐ ⚠️ Not in zone NS records
NSb.dns.ripn.net ⚠️ Not in zone NS records
NSd.dns.ripn.net ⚠️ Not in zone NS records
NSe.dns.ripn.net ⚠️ Not in zone NS records
NSf.dns.ripn.net ⚠️ Not in zone NS records
SOAa.dns.ripn.nethostmaster@ripn.net serial=4068310
WOT: SAFE (50/100)

Same first word

Similar names

DNS History

14 records (6 active, 8 former)

20162017201820192020202120222023202420252026NSns1-04.azure-dns.comns2-04.azure-dns.netns3-04.azure-dns.orgns4-04.azure-dns.infodns1.yandex.netdns2.yandex.netns1.reg.runs2.reg.ruMXmx.yandex.netA20.101.75.15413.81.111.175191.239.210.24552.166.141.3293.188.40.112
β—‹NSdns1.yandex.net2016-09-15 β†’ 2017-04-06 Β· 5 obs
β—‹ 2016-04-08 14:08:10
● 2016-09-15 15:48:52
● 2017-04-06 06:05:26
β—‹ 2021-03-16 13:12:00
β—‹ 2026-03-28 21:19:08
β—‹NSdns2.yandex.net2016-09-15 β†’ 2017-04-06 Β· 5 obs
β—‹ 2016-04-08 14:08:10
● 2016-09-15 15:48:52
● 2017-04-06 06:05:26
β—‹ 2021-03-16 13:12:00
β—‹ 2026-03-28 21:19:08
●NSns1-04.azure-dns.com2021-03-16 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-06 06:05:26
● 2021-03-16 13:12:00
● 2026-03-28 21:19:08
β—‹NSns1.reg.ru2015-05-28 β†’ 2015-12-29 Β· 4 obs
● 2015-05-28 20:16:04
● 2015-12-29 21:11:24
β—‹ 2016-04-08 14:08:10
β—‹ 2026-03-28 21:19:08
●NSns2-04.azure-dns.net2021-03-16 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-06 06:05:26
● 2021-03-16 13:12:00
● 2026-03-28 21:19:08
β—‹NSns2.reg.ru2015-05-28 β†’ 2015-12-29 Β· 4 obs
● 2015-05-28 20:16:04
● 2015-12-29 21:11:24
β—‹ 2016-04-08 14:08:10
β—‹ 2026-03-28 21:19:08
●NSns3-04.azure-dns.org2021-03-16 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-06 06:05:26
● 2021-03-16 13:12:00
● 2026-03-28 21:19:08
●NSns4-04.azure-dns.info2021-03-16 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-06 06:05:26
● 2021-03-16 13:12:00
● 2026-03-28 21:19:08
●MXmx.yandex.net2016-09-15 β†’ 2026-03-28 Β· 5 obs
● 2016-09-15 15:48:52
● 2017-04-06 06:05:26
β—‹ 2021-03-16 13:12:00
β—‹ 2021-03-25 21:29:50
● 2026-03-28 21:19:08
β—‹A13.81.111.1752017-04-06 β†’ 2017-04-06 Β· 4 obs
β—‹ 2016-09-15 15:48:52
● 2017-04-06 06:05:26
β—‹ 2021-03-16 13:12:00
β—‹ 2026-03-28 21:19:08
β—‹A191.239.210.2452016-09-15 β†’ 2016-09-15 Β· 4 obs
β—‹ 2016-04-08 14:08:10
● 2016-09-15 15:48:52
β—‹ 2017-04-06 06:05:26
β—‹ 2026-03-28 21:19:08
●A20.101.75.1542026-03-28 β†’ 2026-03-28 Β· 2 obs
β—‹ 2021-03-25 21:29:50
● 2026-03-28 21:19:08
β—‹A52.166.141.322021-03-16 β†’ 2021-03-25 Β· 4 obs
β—‹ 2017-04-06 06:05:26
● 2021-03-16 13:12:00
● 2021-03-25 21:29:50
β—‹ 2026-03-28 21:19:08
β—‹A93.188.40.1122015-05-28 β†’ 2015-12-29 Β· 4 obs
● 2015-05-28 20:16:04
● 2015-12-29 21:11:24
β—‹ 2016-04-08 14:08:10
β—‹ 2026-03-28 21:19:08

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
rua.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net...-
internetcars.runs2-04.azure-dns.net, ns1-04.azure-dns.com-

βœ… Authoritative Response

Server:150.171.21.4

NS records: ns2-04.azure-dns.net, ns1-04.azure-dns.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for internetcars.ru (unsigned zone)

⏱️ Timing

Total: 657ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A120.101.75.154
NS4ns1-04.azure-dns.com, ns2-04.azure-dns.net...
MX1mx.yandex.net (pri: 10)
TXT1_globalsign-domain-verification=_rQtZFWA
SOA1ns1-04.azure-dns.com azuredns-hostmaster

Analysis

IP Addresses

internetcars.ru points to a single IP number: 20.101.75.154.

Name Servers

internetcars.ru is delegated to four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

internetcars.ru at least partially shares name servers with other domains, for instance effectivemeetings.com, if.gl, microsoft-365-support.com, ci.com.br and 98.107.131.in-addr.arpa.

Host names with two IP numbers:

ns1-04.azure-dns.com points to: 2603:1061:0:700::4 and 13.107.236.4.

ns4-04.azure-dns.info points to: 2620:1ec:bda:700::4 and 208.84.5.4.

ns2-04.azure-dns.net points to: 2620:1ec:8ec:700::4 and 150.171.21.4.

ns3-04.azure-dns.org points to: 2a01:111:4000:700::4 and 204.14.183.4.

Mail Servers

internetcars.ru is handled by a single mail server, mx.yandex.net.

internetcars.ru uses the same mail server configuration as other domains, such as cleanfix.ru, milonga.ru, bta-group.ru, kostus.pro and krealikum.ru.

internetcars.ru shares at least some mail servers with other domains, for instance marketguru.io, kamatrucks.ru, stabit.ru and lancer-club.spb.ru.

mx.yandex.net resolves to two IP numbers: 2a02:6b8::311 and 77.88.21.249.