linkedin.ph - robtex.com

linkedin.ph

DNSSEC⚠️ Not signed
A2620:109:c002::6cae:a18πŸ‡ΊπŸ‡Έ LINKEDIN-12620:109:c002::/48 LinkedIn 2029 Stierlin Ct Mountain View, CA 94043
A108.174.10.24πŸ‡ΊπŸ‡Έ LINKEDIN-1108.174.10.0/24 Linkedin 2029 Stierlin Ct Mountain View, CA 94043 USA
NSns1-42.azure-dns.com ⭐
A150.171.10.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
PTRns1-42.azure-dns.com
NSns2-42.azure-dns.net
A150.171.16.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
PTRns2-42.azure-dns.net
NSns3-42.azure-dns.org
A13.107.222.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
PTRns3-42.azure-dns.org
NSns4-42.azure-dns.info
A13.107.206.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
PTRns4-42.azure-dns.info
TXTv=spf1 -all
SOAns1-42.azure-dns.comazuredns-hostmaster@microsoft.com serial=1

ph

DNSSECπŸ”’ Signed (DS record present)
NSph-tld-ns.dot.ph ⭐
NS1.ns.ph
NSns2.cuhk.edu.hk
NSns4.apnic.net
NSph.communitydns.net
SOAph-tld-ns.dot.phsysadmin@domains.ph 2026-05-02 #13

Same first word

Similar names

DNS History

16 records (6 active, 10 former)

20192020202120222023202420252026NSns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.infons1.markmonitor.comns2.markmonitor.comns3.markmonitor.comns4.markmonitor.comns5.markmonitor.comns6.markmonitor.comns7.markmonitor.comMXA108.174.10.242620:109:c002::6cae:a18108.174.10.142620:109:c002::6cae:a0e
●NSns1-42.azure-dns.com2026-04-30 β†’ 2026-05-02 Β· 3 obs
β—‹ 2021-10-07 07:56:08
● 2026-04-30 14:52:38
● 2026-05-02 06:46:24
β—‹NSns1.markmonitor.com2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
●NSns2-42.azure-dns.net2026-04-30 β†’ 2026-05-02 Β· 3 obs
β—‹ 2021-10-07 07:56:08
● 2026-04-30 14:52:38
● 2026-05-02 06:46:24
β—‹NSns2.markmonitor.com2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
●NSns3-42.azure-dns.org2026-04-30 β†’ 2026-05-02 Β· 3 obs
β—‹ 2021-10-07 07:56:08
● 2026-04-30 14:52:38
● 2026-05-02 06:46:24
β—‹NSns3.markmonitor.com2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
●NSns4-42.azure-dns.info2026-04-30 β†’ 2026-05-02 Β· 3 obs
β—‹ 2021-10-07 07:56:08
● 2026-04-30 14:52:38
● 2026-05-02 06:46:24
β—‹NSns4.markmonitor.com2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
β—‹NSns5.markmonitor.com2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
β—‹NSns6.markmonitor.com2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
β—‹NSns7.markmonitor.com2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
β—‹MX(root)2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
β—‹A108.174.10.142018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
●A108.174.10.242026-04-30 β†’ 2026-05-02 Β· 3 obs
β—‹ 2021-10-07 07:56:08
● 2026-04-30 14:52:38
● 2026-05-02 06:46:24
β—‹A2620:109:c002::6cae:a0e2018-11-28 β†’ 2021-10-07 Β· 4 obs
● 2018-11-28 16:01:52
● 2021-10-07 07:56:08
β—‹ 2026-04-30 14:52:38
β—‹ 2026-05-02 06:46:24
●A2620:109:c002::6cae:a182026-04-30 β†’ 2026-05-02 Β· 3 obs
β—‹ 2021-10-07 07:56:08
● 2026-04-30 14:52:38
● 2026-05-02 06:46:24

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
ph1.ns.ph, ph.communitydns.net, ns2.cuhk.edu.hk, ns4.apnic.net-
linkedin.phns1-42.azure-dns.com, ns3-42.azure-dns.org, ns2-42.azure-dns.net, ns4-42.azure-dns.info-

βœ… Authoritative Response

Server:150.171.10.42

NS records: ns1-42.azure-dns.com, ns3-42.azure-dns.org, ns2-42.azure-dns.net, ns4-42.azure-dns.info

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkedin.ph (unsigned zone)

⏱️ Timing

Total: 514ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1108.174.10.24
AAAA12620:109:c002::6cae:a18
NS4ns1-42.azure-dns.com, ns2-42.azure-dns.net...
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns1-42.azure-dns.com azuredns-hostmaster

Analysis

IP Addresses

linkedin.ph has two IP numbers: 2620:109:c002::6cae:a18 and 108.174.10.24.

Other host names, for instance linked.in, linkedin.com.mx, rapportive.com, linkedin-ela4.com and digitalmarketingremix.com share IP numbers with linkedin.ph.

Name Servers

linkedin.ph delegates to four name servers: ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.

linkedin.ph at least partially shares name servers with other domains, including linkedin.name, linkedin.mk, oncall.tools, snaphired.com and leetcoder.com.

These name servers are commonly used with dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, 1.ns.linkedin.com, 2.ns.linkedin.com, 3.ns.linkedin.com, 4.ns.linkedin.com, 5.ns.linkedin.com and 6.ns.linkedin.com.

Host names with one IP number:

ns1-42.azure-dns.com points to 150.171.10.42; ns4-42.azure-dns.info points to 13.107.206.42; ns2-42.azure-dns.net points to 150.171.16.42; ns3-42.azure-dns.org points to 13.107.222.42.