Hostname
ydesigngroup.com
Last fetched
ydesigngroup.com resolves to 54.193.57.226, announced in 54.193.0.0/17 by AMAZON-02 - Amazon.com, Inc. in US. ydesigngroup.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 54.193.57.226
54.193.0.0/17 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
IPv6 resolution
No AAAA record for ydesigngroup.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- domains@ydesigngroup.com, ylighting@yahoo.com
Subdomains
Showing 12 of 19. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Sample outbound links
Mail and authentication
Nameservers
- ns-498.awsdns-62.com
- ns-785.awsdns-34.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1222.awsdns-24.org
- ns-1614.awsdns-09.co.uk
MX records
- ydesigngroup-com.mail.protection.outlook.com
- mx1-us1.ppe-hosted.com
- mx2-us1.ppe-hosted.com
SPF policy
- ip: 167.216.128.0/22
- ip: 216.34.99.11/32
- ip: 216.34.99.12/30
- ip: 216.34.99.16/30
- ip: 216.34.99.22/32
- include: sent-via.netsuite.com
- include: spf.protection.outlook.com
- include: a:dispatch-us.ppe-hosted.com
- a: ydesigngroup.com
- mx: ydesigngroup.com
- a: production.web.lumens.demandware.net
- include: sendgrid.net
- ip: 195.162.89.188
- ip: 216.34.99.21
- ip: 216.34.99.60
- ip: 54.201.32.223
Threat-feed evidence
History
Related pages
Pivot from ydesigngroup.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "ydesigngroup.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.