eviry.com - dns.ninja

`eviry.com`

DNSSEC	⚠️ Not signed
A	13.196.63.53^{🇺🇸 Amazon13.192.0.0/13}
		PTR	`ec2-13-196-63-53.ap-northeast-1.compute.amazonaws.com`
A	35.78.131.188^{🇯🇵 Amazon35.72.0.0/13 EC2 NRT prefix}
NS	`ns-794.awsdns-35.net` ⭐
		A	2600:9000:5303:1a00::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-794.awsdns-35.net`
		A	205.251.195.26^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-794.awsdns-35.net`
NS	`ns-1050.awsdns-03.org`
		A	2600:9000:5304:1a00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1050.awsdns-03.org`
		A	205.251.196.26^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1050.awsdns-03.org`
NS	`ns-1886.awsdns-43.co.uk`
		A	2600:9000:5307:5e00::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1886.awsdns-43.co.uk`
		A	205.251.199.94^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1886.awsdns-43.co.uk`
NS	`ns-87.awsdns-10.com`
		A	2600:9000:5300:5700::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-87.awsdns-10.com`
		A	205.251.192.87^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-87.awsdns-10.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c08::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f27.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽²⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽³⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`mx.sendgrid.net`⁽⁴⁰⁾
		A	3.17.120.38^{🇺🇸 Amazon3.16.0.0/14 EC2 CMH prefix}
			PTR	`ec2-3-17-120-38.us-east-2.compute.amazonaws.com`
		A	3.136.245.72^{🇺🇸 Amazon3.136.0.0/13 EC2 CMH prefix}
			PTR	`ec2-3-136-245-72.us-east-2.compute.amazonaws.com`
		A	13.216.54.185^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-216-54-185.compute-1.amazonaws.com`
		A	15.222.160.229^{🇨🇦 Amazon15.222.0.0/15 EC2 YUL prefix}
			PTR	`ec2-15-222-160-229.ca-central-1.compute.amazonaws.com`
		A	16.52.61.209^{🇺🇸 Amazon16.52.0.0/16 EC2 YUL prefix}
			PTR	`ec2-16-52-61-209.ca-central-1.compute.amazonaws.com`
		A	16.52.110.174^{🇺🇸 Amazon16.52.0.0/16 EC2 YUL prefix}
			PTR	`ec2-16-52-110-174.ca-central-1.compute.amazonaws.com`
		A	18.224.101.244^{🇺🇸 Amazon18.224.0.0/14 EC2 CMH prefix}
			PTR	`ec2-18-224-101-244.us-east-2.compute.amazonaws.com`
		A	34.198.67.24^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-198-67-24.compute-1.amazonaws.com`
		A	44.216.124.122^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-216-124-122.compute-1.amazonaws.com`
		A	44.245.249.202^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
			PTR	`ec2-44-245-249-202.us-west-2.compute.amazonaws.com`
		A	52.25.213.239^{🇺🇸 Amazon52.24.0.0/14 EC2 PDX prefix}
			PTR	`ec2-52-25-213-239.us-west-2.compute.amazonaws.com`
		A	52.37.49.26^{🇺🇸 Amazon52.36.0.0/14 EC2 PDX prefix}
			PTR	`ec2-52-37-49-26.us-west-2.compute.amazonaws.com`
TXT	`00D0o000001Qt8K=1TBRC00000004jZ`
TXT	`MS=ms78848862`
TXT	`google-site-verification=2z-h7RKBUDjLfCXIczP_h5GCwp0Rm0GK4X7gFDNbInM`
TXT	`google-site-verification=El7ittMrb9DYkOaN9Xut7tJ698e9a-XfzCRsR4J91Qo`
TXT	`google-site-verification=HB3Qd-YEDtCLE_6v6qPrgBVukZtFjrncYwgejy75Bbk`
TXT	`google-site-verification=usdkfHnG4qscJstJJOHzsmjEShMtCHqm13Iyiz652xc`
TXT	`google-site-verification=w8y7vW-BWHVrZmYmUoVZAEY7yWeBAu1cBRhIwzuvrfs`
TXT	`k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCaJGp7FHUb4/ul9vlO5sBY4YQ...`
TXT	`pardot967273=617538f5f557e96d67b0ce3b0e33532a5cf8e35c0e0db521ebaac4919a75178a`
TXT	`sending_domain1043741=20efa5a0f2d0ed5ce046cf139972c76a9c33ec276a4e9b7574fb98a...`
TXT	`v=spf1 include:_spf.google.com include:kagoya.net include:_spf.salesforce.com...`
TXT	`v=spf1 include:sendgrid.net ~all`
TXT	`v=spf1 ip4:52.196.223.252 ip4:18.182.137.60 -all`
SOA	`ns-794.awsdns-35.net`awsdns-hostmaster@amazon.com 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=1782106480

Previously MX for

eviry.com

Same first word

eviry.com

Similar names

veriy.in

yreiv.com

viyer.com

veiry.com

viyer.net

reiyv.com

viyer.in

veyri.com

veriy.com

ivery.tools

reyvi.com

yveri.com

ivery.se

vyeri.com

yiver.com

ivery.co.uk

viery.com

rivey.workers.dev

ivery.eu

yeriv.com

ivery.net

ivery.in

veriy.net

ivyer.net

ivrey.com

ivery.ru

eryiv.blogspot.tw

rivey.com

vyire.com

erivy.com

eyrvi.com

ivyer.com

veiry.net

reyvi.net.br

ivery.com

DNS History

22 records (11 active, 11 former)

○NS01.dnsv.jp2007-12-20 → 2017-11-20 · 4 obs

● 2007-12-20 23:15:04
● 2017-11-20 07:21:40
○ 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

○NS02.dnsv.jp2007-12-20 → 2017-11-20 · 4 obs

● 2007-12-20 23:15:04
● 2017-11-20 07:21:40
○ 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

○NS03.dnsv.jp2015-05-31 → 2017-11-20 · 5 obs

○ 2007-12-20 23:15:04
● 2015-05-31 12:10:28
● 2017-11-20 07:21:40
○ 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

○NS04.dnsv.jp2015-05-31 → 2017-11-20 · 5 obs

○ 2007-12-20 23:15:04
● 2015-05-31 12:10:28
● 2017-11-20 07:21:40
○ 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

●NSns-1050.awsdns-03.org2026-04-24 → 2026-06-22 · 3 obs

○ 2017-11-20 07:21:40
● 2026-04-24 19:27:46
● 2026-06-22 05:36:22

●NSns-1886.awsdns-43.co.uk2026-04-24 → 2026-06-22 · 3 obs

○ 2017-11-20 07:21:40
● 2026-04-24 19:27:46
● 2026-06-22 05:36:22

●NSns-794.awsdns-35.net2026-04-24 → 2026-06-22 · 3 obs

○ 2017-11-20 07:21:40
● 2026-04-24 19:27:46
● 2026-06-22 05:36:22

●NSns-87.awsdns-10.com2026-04-24 → 2026-06-22 · 3 obs

○ 2017-11-20 07:21:40
● 2026-04-24 19:27:46
● 2026-06-22 05:36:22

●MXalt1.aspmx.l.google.com2015-05-31 → 2026-06-22 · 3 obs

○ 2007-12-20 23:15:04
● 2015-05-31 12:10:28
● 2026-06-22 05:36:22

●MXalt2.aspmx.l.google.com2015-05-31 → 2026-06-22 · 3 obs

○ 2007-12-20 23:15:04
● 2015-05-31 12:10:28
● 2026-06-22 05:36:22

●MXaspmx.l.google.com2015-05-31 → 2026-06-22 · 3 obs

○ 2007-12-20 23:15:04
● 2015-05-31 12:10:28
● 2026-06-22 05:36:22

●MXaspmx2.googlemail.com2015-05-31 → 2026-06-22 · 3 obs

○ 2007-12-20 23:15:04
● 2015-05-31 12:10:28
● 2026-06-22 05:36:22

○MXeviry.com2007-12-20 → 2007-12-20 · 3 obs

● 2007-12-20 23:15:04
○ 2015-05-31 12:10:28
○ 2026-06-22 05:36:22

●MXmx.sendgrid.net2026-04-24 → 2026-06-22 · 3 obs

○ 2015-05-31 12:10:28
● 2026-04-24 19:27:46
● 2026-06-22 05:36:22

○A124.40.6.1452007-12-20 → 2007-12-20 · 3 obs

● 2007-12-20 23:15:04
○ 2015-05-31 12:10:28
○ 2026-06-22 05:36:22

○A13.159.154.1472026-04-24 → 2026-06-22 · 2 obs

○ 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

●A13.196.63.532026-06-22 → 2026-06-22 · 2 obs

○ 2026-04-24 19:27:46
● 2026-06-22 05:36:22

●A35.78.131.1882026-06-22 → 2026-06-22 · 2 obs

○ 2026-04-24 19:27:46
● 2026-06-22 05:36:22

○A49.212.179.1002015-05-31 → 2017-11-20 · 5 obs

○ 2007-12-20 23:15:04
● 2015-05-31 12:10:28
● 2017-11-20 07:21:40
○ 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

○A52.197.179.2332026-04-24 → 2026-04-24 · 3 obs

○ 2017-11-20 07:21:40
● 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

○A52.197.59.482026-04-24 → 2026-04-24 · 3 obs

○ 2017-11-20 07:21:40
● 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

○A52.197.88.1922026-04-24 → 2026-06-22 · 2 obs

○ 2026-04-24 19:27:46
○ 2026-06-22 05:36:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net, g.gtld-servers.net...	-
eviry.com	ns-87.awsdns-10.com, ns-794.awsdns-35.net, ns-1050.awsdns-03.org, ns-1886.awsdns-43.co.uk	2 records

✅ Authoritative Response

Server:205.251.199.94

NS records: ns-87.awsdns-10.com, ns-794.awsdns-35.net, ns-1050.awsdns-03.org, ns-1886.awsdns-43.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for eviry.com (unsigned zone)

⏱️ Timing

Total: 422ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`35.78.131.188, 13.196.63.53`
NS	4	`ns-1050.awsdns-03.org, ns-1886.awsdns-43.co.uk...`
MX	5	`aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)...`
TXT	13	`00D0o000001Qt8K=1TBRC00000004jZ, MS=ms78848862...`
SOA	1	`ns-794.awsdns-35.net awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-87.awsdns-10.com, ns-87.awsdns-10.com)

Analysis

IP Addresses

eviry.com points to the IP addresses 13.196.63.53 and 35.78.131.188

Name Servers

The NS records for eviry.com point to four name servers: ns-87.awsdns-10.com, ns-794.awsdns-35.net, ns-1050.awsdns-03.org and ns-1886.awsdns-43.co.uk.

At least some of eviry.com's name servers are shared with other domains, for example ezcircular.com, notebookstore.cl, rsprogram.ca and two more.

It is common for these name servers to be used in conjunction with the name servers ns-999.awsdns-60.net, ns-1070.awsdns-05.org and ns-1601.awsdns-08.co.uk.

Four hostnames, each resolving to a pair of IP addresses: ns-87.awsdns-10.com directs to 205.251.192.87 and 2600:9000:5300:5700::1; ns-794.awsdns-35.net directs to 205.251.195.26 and 2600:9000:5303:1a00::1; ns-1050.awsdns-03.org directs to 205.251.196.26 and 2600:9000:5304:1a00::1; ns-1886.awsdns-43.co.uk directs to 205.251.199.94 and 2600:9000:5307:5e00::1.

Mail Servers

eviry.com has five mail servers, which are aspmx2.googlemail.com, mx.sendgrid.net, aspmx.l.google.com and two others.

There is at least a partial MX overlap between eviry.com and other domains, including tmsmit.com, synthesizellc.com, thrustme.com and two others.

These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 4 others.

DNS names with 12 IP addresses:

mx.sendgrid.net resolves to 3.17.120.38, 3.136.245.72 and 13.216.54.185 among others, with 9 other IP addresses in total.

Host names that have two IP addresses:

aspmx2.googlemail.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.

aspmx.l.google.com resolves to two addresses: 64.233.180.26 and 2607:f8b0:4004:c08::1b.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c0f::1a IP addresses.