Hostname
doorfoldpartition.com
Last fetched
doorfoldpartition.com resolves to 34.194.230.197, announced in 34.192.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. doorfoldpartition.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
- 34.194.230.197
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.206.226.128
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.226.108.190
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.226.173.208
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.170.162.202
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.218.163.250
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.22.188.38
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.5.79.106
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.144.110.242
54.144.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.160.80.254
54.160.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.88.168.115
54.88.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.172.4.244
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.95.78.20
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.230.100.93
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 184.192.95.139
184.192.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.56.68.76
IPv6 resolution
No AAAA record for doorfoldpartition.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:420
- Registrant organisation
- guang zhou shi de fu ping feng zhuang shi gong cheng you xian gong si
- Contact emails
- 3225452618@qq.com
Company
- Company
- Guangzhou Doorfold Partition Wall Co., Ltd.
- Industry
- Hospitality
- Headquarters
- Guangzhou, China
Technology
Guangzhou Doorfold Partition Wall Co., Ltd. has been observed using 29 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- Open Graph · content management system
- PHP · programming languages
- Google Analytics · intelligence and analytics
- Priority Hints · performance
- Nginx · web servers
- JSON-LD · frameworks and libraries
- Google Tag Manager · tag management
- Amazon Web Services · cloud hosting
- Facebook · social media analytics and monitoring
- Swiper · javascript libraries
- Facebook Pixel · analytics
- YouTube · online community software
- OpenResty · development
- DoubleClick Floodlight · advertising
- Google Ads · advertising
- Google Ads Conversion Tracking · advertising
- HTML5 Mobile Boilerplate · mobile application development platforms
- Alibaba Cloud DNS · domain name services
- Amazon CloudFront · content delivery network
- HiChina · cloud hosting
Peer companies
Subdomains
Showing 2 of 2 subdomains (2 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.
Sample inbound links
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for doorfoldpartition.com.
DKIM signing
No DKIM signing vendor is attributed to doorfoldpartition.com in WhisperGraph.
Nameservers
- ns-235.awsdns-29.com
- dns10.hichina.com
- dns9.hichina.com
- ns-934.awsdns-52.net
- ns-1119.awsdns-11.org
- ns-1793.awsdns-32.co.uk
MX records
- mxn.mxhichina.com
- mxw.mxhichina.com
SPF policy
- include: spf.mxhichina.com
Threat-feed evidence
History
Related pages
Pivot from doorfoldpartition.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)
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)
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.