Hostname
swy7.com
Last fetched
swy7.com resolves to 1.194.173.140, announced in 1.194.173.0/24 by CHINANET-Henan-Zhengzhou-Shujugang-IDC - China Telecom Henan Zhengzhou Shujugang IDC network in CN. swy7.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
- 1.194.173.140
1.194.173.0/24 · CHINANET-Henan-Zhengzhou-Shujugang-IDC - China Telecom Henan Zhengzhou Shujugang IDC network
- 1.194.217.10
1.194.216.0/23 · CHINANET-Henan-Zhengzhou-Shujugang-IDC - China Telecom Henan Zhengzhou Shujugang IDC network
- 104.21.46.126
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 111.172.211.148
111.172.208.0/22 · CHINATELECOM-Hubei-IDC - CHINANET Hubei province network
- 111.48.138.116
111.48.138.0/24 · CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd. · Guangzhou, CN
- 111.6.201.146
111.6.200.0/21 · CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd. · Guangzhou, CN
- 111.6.225.189
111.6.224.0/21 · CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd. · Guangzhou, CN
- 111.7.66.168
111.7.64.0/20 · CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd. · Guangzhou, CN
- 123.53.183.213
123.53.180.0/22 · CHINANET-Henan-Luoyang-IDC - Henan Luoyang IDC
- 123.6.0.70
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 123.6.179.111
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 123.6.180.115
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 123.6.72.100
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 124.232.161.232
124.232.161.0/24 · CT-HuNan-Changsha-IDC - No.293,Wanbao Avenue · Qingyuan, CN
- 172.67.139.4
172.67.128.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 183.94.165.71
183.92.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Wuhan, CN
- 171.15.110.132
171.15.108.0/22 · CHINATELECOM-HENAN-LUOYANG-IDC - Luoyang, Henan Province, P.R.China.
- 42.236.77.100
42.224.0.0/12 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 118.252.196.104
118.252.192.0/21 · CT-HuNan-Changsha-IDC - No.293,Wanbao Avenue · Qingyuan, CN
- 122.191.142.102
122.188.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Wuhan, CN
IPv6 resolution
No AAAA record for swy7.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:3758
- Registrant organisation
- hu nan bi kao wang luo ke ji you xian gong si
- Contact emails
- info@privatename.com
Company
- Company
- swy7
Technology
swy7 has been observed using 5 technologies somewhere in its estate. This is observed use, not an exposure finding.
- jQuery · javascript libraries
- Open Graph · content management system
- Nginx · web servers
- Baidu Analytics · analytics
- DNSPod · domain name services
Subdomains
Showing 4 of 4 subdomains (4 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for swy7.com.
DKIM signing
No DKIM signing vendor is attributed to swy7.com in WhisperGraph.
Nameservers
- ns3.bytedns.com
- ns4.bytedns.com
- ns9.bytedns.com
- annalise.ns.cloudflare.com
- skip.ns.cloudflare.com
- francis.dnspod.net
- zara.dnspod.net
Threat-feed evidence
History
Related pages
Pivot from swy7.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.