appforceblog.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`appforceblog.com`

DNSSEC	⚠️ Not signed
A	3.33.139.32^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`aeedc42b70c898c66.awsglobalaccelerator.com`
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2.markmonitor.com`
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com`
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com`
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com` ⚠️ Not in parent delegation
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2020-01-30 #2

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1787052804

Same first word

appforceblog.com

Previous names

Next names

DNS History

14 records (8 active, 6 former)

○NSdns01.salesforce.com2015-07-21 → 2017-03-30 · 4 obs

● 2015-07-21 12:34:00
● 2017-03-30 16:54:18
○ 2026-03-16 18:06:24
○ 2026-08-18 11:56:20

○NSdns02.salesforce.com2015-07-21 → 2017-03-30 · 4 obs

● 2015-07-21 12:34:00
● 2017-03-30 16:54:18
○ 2026-03-16 18:06:24
○ 2026-08-18 11:56:20

○NSdns03.salesforce.com2015-07-21 → 2017-03-30 · 4 obs

● 2015-07-21 12:34:00
● 2017-03-30 16:54:18
○ 2026-03-16 18:06:24
○ 2026-08-18 11:56:20

○NSdns04.salesforce.com2015-07-21 → 2017-03-30 · 4 obs

● 2015-07-21 12:34:00
● 2017-03-30 16:54:18
○ 2026-03-16 18:06:24
○ 2026-08-18 11:56:20

○NSdns05.salesforce.com2015-07-21 → 2017-03-30 · 4 obs

● 2015-07-21 12:34:00
● 2017-03-30 16:54:18
○ 2026-03-16 18:06:24
○ 2026-08-18 11:56:20

○NSdns06.salesforce.com2015-07-21 → 2017-03-30 · 4 obs

● 2015-07-21 12:34:00
● 2017-03-30 16:54:18
○ 2026-03-16 18:06:24
○ 2026-08-18 11:56:20

●NSns1.markmonitor.com2026-03-16 → 2026-08-18 · 3 obs

○ 2017-03-30 16:54:18
● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

●NSns2.markmonitor.com2026-03-16 → 2026-08-18 · 3 obs

○ 2017-03-30 16:54:18
● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

●NSns3.markmonitor.com2026-03-16 → 2026-08-18 · 3 obs

○ 2017-03-30 16:54:18
● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

●NSns4.markmonitor.com2026-03-16 → 2026-08-18 · 3 obs

○ 2017-03-30 16:54:18
● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

●NSns5.markmonitor.com2026-03-16 → 2026-08-18 · 3 obs

○ 2017-03-30 16:54:18
● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

●NSns6.markmonitor.com2026-03-16 → 2026-08-18 · 3 obs

○ 2017-03-30 16:54:18
● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

●NSns7.markmonitor.com2026-03-16 → 2026-08-18 · 3 obs

○ 2017-03-30 16:54:18
● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

●A3.33.139.322026-03-16 → 2026-08-18 · 2 obs

● 2026-03-16 18:06:24
● 2026-08-18 11:56:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
appforceblog.com	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com...	12 records

✅ Authoritative Response

Server:176.97.158.1

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns2.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for appforceblog.com (unsigned zone)

⏱️ Timing

Total: 903ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.33.139.32`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)

Analysis

IP Addresses

appforceblog.com resolves to just one IP address, 3.33.139.32.

Two other host names, along with fireliveassist.com, roxygirl.com and sportography.com, also share IP numbers with appforceblog.com.

Name Servers

appforceblog.com is served by 7 authoritative name servers — among them ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 others.

appforceblog.com partially shares its NS delegation with several other domains, including gsbchemical.com.au, rtspecialityinsurance.com, tommy-hilfiger.com.uy and two others.

The name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com are often found in use alongside these name servers.

Host names that have two IP addresses:

ns1.markmonitor.com resolves to two addresses: 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com resolves to two addresses: 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com resolves to two addresses: 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com resolves to two addresses: 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com resolves to two addresses: 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com resolves to two addresses: 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com resolves to two addresses: 149.112.161.2 and 2620:10a:80a9::2.