firecom.com - dns.ninja

firecom.com

DNSSEC⚠️ Not signed
A141.193.213.10πŸ‡ΊπŸ‡Έ CLOUDFLARESPECTRUM141.193.213.0/24 WPEngine, Inc. 504 Lavaca Street, 1000, Austin, TX 78701, US
NSdns101.register.com ⭐
A162.159.24.117Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSdns102.register.com
A162.159.25.158Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
MXfirecom-com.mail.protection.outlook.com ⭐
A2a01:111:f403:c927::1πŸ‡ΊπŸ‡Έ Microsoft2a01:111:f000::/36
PTRmail-bn8pr05cu00301.inbound.protection.outlook.com
A2a01:111:f403:c946::3πŸ‡ΊπŸ‡Έ Microsoft2a01:111:f000::/36
PTRmail-ch0pr04cu00603.inbound.protection.outlook.com
A2a01:111:f403:c946::6πŸ‡ΊπŸ‡Έ Microsoft2a01:111:f000::/36
PTRmail-ch5pr02cu00406.inbound.protection.outlook.com
A2a01:111:f403:f90f::1πŸ‡ΊπŸ‡Έ Microsoft2a01:111:f000::/36
PTRmail-sa9pr04cu00201.inbound.protection.outlook.com
A52.101.11.3πŸ‡ΊπŸ‡Έ Microsoft52.96.0.0/12 MICROSOFT
PTRmail-sn1pr0501cu00103.inbound.protection.outlook.com
A52.101.11.9πŸ‡ΊπŸ‡Έ Microsoft52.96.0.0/12 MICROSOFT
PTRmail-sn1pr02cu00101.inbound.protection.outlook.com
A52.101.41.3πŸ‡ΊπŸ‡Έ Microsoft52.96.0.0/12 MICROSOFT
PTRmail-sj2pr05cu00103.inbound.protection.outlook.com
A52.101.194.0πŸ‡ΊπŸ‡Έ Microsoft52.96.0.0/12 MICROSOFT
PTRmail-ch5pr02cu00200.inbound.protection.outlook.com
TXTv=spf1 mx include:spf.protection.outlook.com include:_spf.act-on.net include:...
SOADNS101.REGISTER.comroot@REGISTER.com serial=126010210

com

WOT: SAFE (70/100)

Subdomains

Same first word

Similar names

DNS History

14 records (4 active, 10 former)

20162017201820192020202120222023202420252026NSdns101.register.comdns102.register.comdns010.d.register.comdns029.c.register.comdns090.b.register.comdns094.a.register.comdns1.stabletransit.comdns2.stabletransit.comMXfirecom-com.mail.protection.outlook.comfirecom-com.mail.eo.outlook.comA141.193.213.10104.196.163.9745.33.18.18498.129.229.50
β—‹NSdns010.d.register.com2016-04-24 β†’ 2017-09-28 Β· 5 obs
β—‹ 2016-01-18 17:25:08
● 2016-04-24 12:23:54
● 2017-09-28 09:10:28
β—‹ 2026-03-23 23:12:12
β—‹ 2026-07-31 05:59:50
β—‹NSdns029.c.register.com2016-04-24 β†’ 2017-09-28 Β· 5 obs
β—‹ 2016-01-18 17:25:08
● 2016-04-24 12:23:54
● 2017-09-28 09:10:28
β—‹ 2026-03-23 23:12:12
β—‹ 2026-07-31 05:59:50
β—‹NSdns090.b.register.com2016-04-24 β†’ 2017-09-28 Β· 5 obs
β—‹ 2016-01-18 17:25:08
● 2016-04-24 12:23:54
● 2017-09-28 09:10:28
β—‹ 2026-03-23 23:12:12
β—‹ 2026-07-31 05:59:50
β—‹NSdns094.a.register.com2016-04-24 β†’ 2017-09-28 Β· 5 obs
β—‹ 2016-01-18 17:25:08
● 2016-04-24 12:23:54
● 2017-09-28 09:10:28
β—‹ 2026-03-23 23:12:12
β—‹ 2026-07-31 05:59:50
β—‹NSdns1.stabletransit.com2015-05-24 β†’ 2016-01-18 Β· 4 obs
● 2015-05-24 21:05:56
● 2016-01-18 17:25:08
β—‹ 2016-04-24 12:23:54
β—‹ 2026-07-31 05:59:50
●NSdns101.register.com2026-03-23 β†’ 2026-07-31 Β· 3 obs
β—‹ 2017-09-28 09:10:28
● 2026-03-23 23:12:12
● 2026-07-31 05:59:50
●NSdns102.register.com2026-03-23 β†’ 2026-07-31 Β· 3 obs
β—‹ 2017-09-28 09:10:28
● 2026-03-23 23:12:12
● 2026-07-31 05:59:50
β—‹NSdns2.stabletransit.com2015-05-24 β†’ 2016-01-18 Β· 4 obs
● 2015-05-24 21:05:56
● 2016-01-18 17:25:08
β—‹ 2016-04-24 12:23:54
β—‹ 2026-07-31 05:59:50
β—‹MXfirecom-com.mail.eo.outlook.com2015-05-24 β†’ 2016-01-18 Β· 4 obs
● 2015-05-24 21:05:56
● 2016-01-18 17:25:08
β—‹ 2016-04-24 12:23:54
β—‹ 2026-07-31 05:59:50
●MXfirecom-com.mail.protection.outlook.com2015-05-24 β†’ 2026-07-31 Β· 2 obs
● 2015-05-24 21:05:56
● 2026-07-31 05:59:50
β—‹A104.196.163.972016-11-16 β†’ 2017-09-28 Β· 5 obs
β—‹ 2016-10-04 02:50:50
● 2016-11-16 09:30:06
● 2017-09-28 10:32:54
β—‹ 2026-03-23 23:12:12
β—‹ 2026-07-31 05:59:50
●A141.193.213.102026-03-23 β†’ 2026-07-31 Β· 3 obs
β—‹ 2017-09-28 10:32:54
● 2026-03-23 23:12:12
● 2026-07-31 05:59:50
β—‹A45.33.18.1842016-04-24 β†’ 2016-10-04 Β· 5 obs
β—‹ 2016-01-18 17:25:08
● 2016-04-24 12:23:54
● 2016-10-04 02:50:50
β—‹ 2016-11-16 09:30:06
β—‹ 2026-07-31 05:59:50
β—‹A98.129.229.502015-05-24 β†’ 2016-01-18 Β· 4 obs
● 2015-05-24 21:05:56
● 2016-01-18 17:25:08
β—‹ 2016-04-24 12:23:54
β—‹ 2026-07-31 05:59:50

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comi.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net...-
firecom.comdns101.register.com, dns102.register.com2 records

βœ… Authoritative Response

Server:162.159.25.158

NS records: dns101.register.com, dns102.register.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for firecom.com (unsigned zone)

⏱️ Timing

Total: 327ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1141.193.213.10
NS2dns102.register.com, dns101.register.com
MX1firecom-com.mail.protection.outlook.com
TXT1v=spf1 mx include:spf.protection.outlook
SOA1DNS101.REGISTER.com root.REGISTER.com

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)

Analysis

Hierarchy

firecom.com is the parent zone for mail.firecom.com.

IP Addresses

firecom.com directs to one IP number, which is 141.193.213.10.

Among the host names that share IP numbers with firecom.com are acteonline.org, pyramidcom.com, americanthing.com and two others.

Name Servers

firecom.com uses two name servers for its delegation: dns101.register.com and dns102.register.com.

firecom.com has the same name server delegation as a number of other domains, such as solarbt.com, mr-sim.com, maxouttech.com and two more.

At least some of firecom.com's name servers are also used by other domains, among them hudsonbayrealty.com.

dns101.register.com resolves to 162.159.24.117. dns102.register.com resolves to 162.159.25.158. Both host names point to a single IP number.

Mail Servers

firecom.com routes its mail through a single mail server, firecom-com.mail.protection.outlook.com.

firecom-com.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.11.3, 52.101.11.9 and 52.101.41.3, along with 5 other.