reactconf.com - dns.ninja

`reactconf.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`ns1.afternic.com`
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net serial=1

`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=1785167657

Subdomains

tickets.reactconf.com

Same first word

reactconf.ir

reactconf.com

reactconf.org

reactconf.com.br

Similar names

DNS History

20 records (4 active, 16 former)

○NSns-1069.awsdns-05.org2017-03-21 → 2020-01-16 · 5 obs

○ 2016-04-15 18:02:14
● 2017-03-21 22:18:44
● 2020-01-16 05:23:12
○ 2026-02-25 14:55:26
○ 2026-07-27 16:15:32

○NSns-1877.awsdns-42.co.uk2017-03-21 → 2020-01-16 · 5 obs

○ 2016-04-15 18:02:14
● 2017-03-21 22:18:44
● 2020-01-16 05:23:12
○ 2026-02-25 14:55:26
○ 2026-07-27 16:15:32

○NSns-494.awsdns-61.com2017-03-21 → 2020-01-16 · 5 obs

○ 2016-04-15 18:02:14
● 2017-03-21 22:18:44
● 2020-01-16 05:23:12
○ 2026-02-25 14:55:26
○ 2026-07-27 16:15:32

●NSns1.afternic.com2026-02-25 → 2026-07-27 · 3 obs

○ 2020-01-16 05:23:12
● 2026-02-25 14:55:26
● 2026-07-27 16:15:32

○NSns11.eapps.com2015-06-22 → 2016-04-15 · 4 obs

● 2015-06-22 09:26:28
● 2016-04-15 18:02:14
○ 2017-03-21 22:18:44
○ 2026-07-27 16:15:32

○NSns12.eapps.com2015-06-22 → 2016-04-15 · 4 obs

● 2015-06-22 09:26:28
● 2016-04-15 18:02:14
○ 2017-03-21 22:18:44
○ 2026-07-27 16:15:32

○NSns13.eapps.com2015-06-22 → 2016-04-15 · 4 obs

● 2015-06-22 09:26:28
● 2016-04-15 18:02:14
○ 2017-03-21 22:18:44
○ 2026-07-27 16:15:32

○NSns14.eapps.com2015-06-22 → 2016-04-15 · 4 obs

● 2015-06-22 09:26:28
● 2016-04-15 18:02:14
○ 2017-03-21 22:18:44
○ 2026-07-27 16:15:32

●NSns2.afternic.com2026-02-25 → 2026-07-27 · 3 obs

○ 2020-01-16 05:23:12
● 2026-02-25 14:55:26
● 2026-07-27 16:15:32

○MXalt1.aspmx.l.google.com2015-06-22 → 2016-01-24 · 4 obs

● 2015-06-22 09:26:28
● 2016-01-24 20:33:40
○ 2016-04-15 18:02:14
○ 2026-07-27 16:15:32

○MXalt2.aspmx.l.google.com2015-06-22 → 2016-01-24 · 4 obs

● 2015-06-22 09:26:28
● 2016-01-24 20:33:40
○ 2016-04-15 18:02:14
○ 2026-07-27 16:15:32

○MXalt3.aspmx.l.google.com2015-06-22 → 2016-01-24 · 4 obs

● 2015-06-22 09:26:28
● 2016-01-24 20:33:40
○ 2016-04-15 18:02:14
○ 2026-07-27 16:15:32

○MXalt4.aspmx.l.google.com2015-06-22 → 2016-01-24 · 4 obs

● 2015-06-22 09:26:28
● 2016-01-24 20:33:40
○ 2016-04-15 18:02:14
○ 2026-07-27 16:15:32

○MXaspmx.l.google.com2015-06-22 → 2016-01-24 · 4 obs

● 2015-06-22 09:26:28
● 2016-01-24 20:33:40
○ 2016-04-15 18:02:14
○ 2026-07-27 16:15:32

●A13.248.169.482026-02-25 → 2026-07-27 · 3 obs

○ 2020-01-16 05:23:12
● 2026-02-25 14:55:26
● 2026-07-27 16:15:32

○A52.218.52.22020-01-16 → 2020-01-16 · 4 obs

○ 2017-03-21 22:18:44
● 2020-01-16 05:23:12
○ 2026-02-25 14:55:26
○ 2026-07-27 16:15:32

○A54.231.133.1782017-03-21 → 2017-03-21 · 4 obs

○ 2016-04-15 18:02:14
● 2017-03-21 22:18:44
○ 2020-01-16 05:23:12
○ 2026-07-27 16:15:32

○A68.169.55.1942015-06-22 → 2015-11-02 · 4 obs

● 2015-06-22 09:26:28
● 2015-11-02 18:59:58
○ 2016-01-24 20:33:40
○ 2026-07-27 16:15:32

○A69.89.9.1782016-01-24 → 2016-04-15 · 5 obs

○ 2015-11-02 18:59:58
● 2016-01-24 20:33:40
● 2016-04-15 18:02:14
○ 2017-03-21 22:18:44
○ 2026-07-27 16:15:32

●A76.223.54.1462026-02-25 → 2026-07-27 · 3 obs

○ 2020-01-16 05:23:12
● 2026-02-25 14:55:26
● 2026-07-27 16:15:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, k.gtld-servers.net, d.gtld-servers.net, a.gtld-servers.net...	-
reactconf.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for reactconf.com (unsigned zone)

⏱️ Timing

Total: 151ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

Hierarchy

tickets.reactconf.com is delegated beneath reactconf.com.

IP Addresses

reactconf.com points to the IP addresses 13.248.169.48 and 76.223.54.146

Among the host names that share IP numbers with reactconf.com are ratiolegis.com, b2b-center.com, eligiblechain.xyz and two others.

Name Servers

reactconf.com has two authoritative name servers — ns1.afternic.com and ns2.afternic.com.

reactconf.com has the same name server delegation as a number of other domains, such as ossmat.com, unta.net, gramofony.com and two more.

There is at least partial name server overlap between reactconf.com and other domains — economytwo.com, pestmail.com, em-s.com and two more among them.

These name servers tend to appear in combination with the name servers verification-ilzyovyxkjcylcmj8rbffy.ns101.verify.hn, verification-rzr7w5fcimjzspcnpdhntv.ns101.verify.hn, verification-d3jclucsp89ganyqbydeny.ns101.verify.hn and verification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn.

Both ns1.afternic.com and ns2.afternic.com have two IP addresses each. ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45; ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45.